Understand how Action Sequences will work in the event of a service interruption
- Last UpdatedApr 24, 2025
- 1 minute read
The following two events can affect the functioning of Action Sequence:
-
A failover, in which is a change to the primary computer responsible for providing the RealTime service.
-
A mode switch, which changes who has control over each dataset.
Service interruptions can be planned or unplanned.
What happens when there is an unplanned failover or mode switch
-
The Action Sequence will go into an Interrupted state.
-
The executing step will typically go into an Interrupted or Cancelled state. However, if the step failed before it could be interrupted, the step will be reported as Failed.
Restarting your action sequence when there is an unplanned failover or mode switch
-
After an unplanned failover or mode switch, you can select the step at which you would like to start the process. For instructions, see Start an Action Sequence at a particular step.
What happens when there is a planned failover or mode switch
-
If you have planned in advance to change the primary computer responsible for the RealTime service, you can Pause your Action Sequence before the failover. For instructions, see Pause an Action Sequence .
Restarting your action sequence after a planned failover or mode switch
-
If your planned failover is complete and you'd like to resume your Action Sequence, it is possible to do so. For instructions, see Resume an Action Sequence.