When I change a condition or an action, which vServices are affected?

Short answer

All the vServices that use the record directly or indirectly are affected; when a condition (Conditions) changes, the vServices that carry the actions (Actions) and profiles using that condition are also affected. The vServices to be affected are listed in the Used in tab in the preview of the condition and of the action. The moment the change is saved, it is applied only to the vServices whose configuration actually changes; in a cluster setup, if Manual Sync Mode is off (default), it is also transferred to the peer device automatically.

How Does It Work?

1. The condition or action is saved with Edit.
2. TR7 regenerates the configuration of every vService that uses the record and compares it with the previous one.
3. The new setting is applied to the vServices whose configuration changes; those that do not change are not touched.
4. In a cluster setup, the change is transferred to the peer device: automatically while Manual Sync Mode is off, and while it is on, only with Synchronize on the Settings → Device Management → HA Clustering & Sync screen.

Used In Tab

Record	What appears in the Used in tab
Condition	The actions and vServices that use the condition (including indirect use through an action)
Action	The vServices that use the action (action preview)

This tab is checked before the change; a change to a record that is not used anywhere does not affect any vService. The Used in tab does not appear for unused records.

Restrictions in TR7

• The Action Type and Execution Level fields of the action cannot be changed after saving; a new action is created for a different type or phase.
• The delete operation does not show or prevent the places of use; the Used in tab is checked before deleting. A deleted condition is removed from the actions in which it is used, from caching rules, and from the Conditional Backend Services, Debug Mode and WAF whitelist condition fields of the vServices; a deleted action is removed from the Actions list of the vServices it is bound to (Conditions · Delete, Actions · Delete).
• To limit the impact, instead of changing the record, a copy of it can be created and bound only to the relevant vService.

Common Misconceptions

• "Only the vService on the screen I am editing is affected." The record is central; every vService that uses it is affected.
• "The Used in tab of the condition shows only direct use." The vServices of the actions that use the condition are also listed.
• "In a cluster, the change has to be made separately on both devices." With the default auto-sync, the change passes to the peer device on its own; Synchronize is needed only while Manual Sync Mode is on.

How it is done in the documentation

• Conditions · The "Used in" tab must be checked
• Actions · The "Used in" tab must be checked
• Conditions · Delete
• HA Clustering & Sync · Manual Sync Mode

Related questions

• Can I use the same condition in more than one vService?
• Can I see how many times an action has been triggered (hit counter, Action Hits)?
• Why is my Action not triggering?