Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
Why is my Action not triggering?
Short answer
The most common causes are that the action has not been added to the Actions field of the vService, that the condition (Conditions) is never met, that an earlier action in the list or a security module terminates the request, and that the wrong phase (On Request / On Response) is selected. Location Redirection and User Authentication (On HTTP request) never run if they are saved without a condition. Whether the action matches is seen by turning on Hit Counter in the action and monitoring the Action Hits section on the Live Stats screen of the vService.
Checklist
| # | Possible cause | How to recognize / solve it |
|---|---|---|
| 1 | The action has not been added to the vService | The Used in tab does not appear in the action preview (action preview); the action is added to the Details → Actions field of the vService and the vService is saved with Save |
| 2 | The vService is disabled | The Status field of the vService is set to Enabled |
| 3 | A condition-required type has been saved without a condition | In Location redirection and User Authentication (On HTTP request) actions, the Conditions cell of the Actions list is empty; a condition is added (Why doesn't a Location Redirection or User Authentication (On HTTP request) action work if I add it without a condition?) |
| 4 | The condition has been deleted | A deleted condition is also removed from the actions in which it is used. An action whose conditions have all been deleted this way becomes unconditional; in condition-required types, it never runs (Conditions · Delete) |
| 5 | An earlier action or module has ended the request | A Block, Show content or redirection action higher up in the list, or WAF / L7 DDoS & Threat Protection, may have terminated the request; the action order and the module logs are examined (If an action blocks or redirects traffic, do the subsequent actions run?) |
| 6 | Phase mismatch | On Request may have been selected for a response header; or the On Response action is expected on a response that TR7 produces itself (What is the difference between On Request and On Response actions?) |
| 7 | Faulty condition logic | In the interface, a new group is connected to the previous group with or by default; and is evaluated before or; the negated form may have been selected by mistake (How do I combine multiple conditions with AND / OR?) |
| 8 | Order effect | Redirect to HTTPS, Advanced CAPTCHA and Traffic Mirroring take effect after the other request actions; a Block further down the list prevents them (In what order do Actions run; how do I change the order?) |
| 9 | Matching detail | Case sensitivity, a wrong matching method or an unexpected Smart Variable value (condition does not match) |
| 10 | TR7 is behind a proxy | Conditions that look at the client IP see the address of the proxy in front; a Trusted Proxy profile is assigned to the HTTP vService |
How to Verify?
- Hit Counter: It is turned on in the action; if the count of the action does not increase in the Live Stats · Action Hits section of the vService, the action does not match.
- Debug Mode and HTTP Logs: They show what happened to the request at which phase (debug tips).
- Conditions column: In the Load Balancer → Actions list, if the cell is empty for a condition-required type, the action never runs; for types that take no condition,
-is written in the cell.
Common Misconceptions
- "Moving the action to the bottom of the list solves every order problem." The moment at which Redirect to HTTPS, Advanced CAPTCHA and Traffic Mirroring take effect does not depend on the list order.
- "When the condition is deleted, the action stops too." A normal action whose only condition is deleted starts to be applied to all the traffic of the vService.
- "An action can be added to a Network vService." Actions are used in HTTP and L7 TCP vServices; there is no Actions field in a Network vService.
How it is done in the documentation
