Summary of Action Sequence messages and alarms

Action sequence completed successfully.

This alarm is displayed when a sequence finishes successfully.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

No response required.

Action sequence failed on step <STEP NAME>: <REASON>.

This alarm is displayed when a sequence fails to finish. The step (name of the sequence step) and the reason for the failure is indicated.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the Alarms will appear in the Alarm Summary and the Events will appear in the Event Summary.

Depending on the supplied reason, you may need to contact your Administrator.

Step <STEP NAME> failed: <ERROR DESCRIPTION>. Retry attempt <EXECUTION ATTEMPT> of <RETRY COUNT>.

This event is displayed when a sequence step fails to finish. The step (name of the sequence step) and the reason for the failure is indicated.

Depending on the supplied reason, you may need to contact your Administrator.

Sequence failed on step <STEP NAME>: ActionSequence <RECORD NAME> failed unexpectedly.

This alarm is displayed when a sequence unexpectedly fails to finish.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the Alarms will appear in the Alarm Summary and the Events will appear in the Event Summary.

Contact your Administrator.

Step <STEP NAME> failed.Proceeding to failure step <STEP NAME>.

This alarm is displayed when a sequence fails and begins executing the failure path.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the Alarms will appear in the Alarm Summary and the Events will appear in the Event Summary.

No response required.

Step <STEP NAME> succeeded.

This event is displayed when a sequence step executes successfully.

No response required.

Action sequence failed on step <STEP NAME>: Set point timed out.

The alarm is displayed when a sequence step fails because the set point timed out.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the Alarms will appear in the Alarm Summary and the Events will appear in the Event Summary.

No response required.

Unable to start the action sequence at the specified step <STEP SLOT NUMBER> as requested by <USER NAME> at <COMPUTER NAME>. Could not find a sequence step record with that slot number.

This event is displayed when the action sequence is unable to start at the specified step because a sequence step record could not be found with that slot number.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

Contact your Administrator.

Failed to start action sequence <RECORD NAME> as requested by <USER NAME> at <COMPUTER NAME>. Could not find the specified step at which to start.

This event is displayed when the action sequence is unable to start at the specified step.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

Contact your Administrator.

Stopping action sequence <RECORD NAME> as requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when a sequence is stopped by you before completion. The step that was executing (name of the Action Sequence Step record) is indicated.

This event always appears in the Event Summary.

No response required.

Action sequence stopped as requested by <USER NAME> at <COMPUTER NAME> at step <STEP SLOT NUMBER>.

This event is displayed when a sequence is fully stopped, as requested by you. The step that was executing (name of the Action Sequence Step record) is indicated.

This event always appears in the Event Summary.

No response required.

Action sequence <RECORD NAME> started as requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when a sequence is started, if it is not inhibited.

No response required.

Action Sequence completed however one or more failures occurred.

This alarm is displayed when a failure occurred on a step during execution, but a failure path existed, and was successfully completed.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

You may wish to look into the reasons for the failure. If necessary, contact your Administrator .

Action sequence <RECORD NAME> started at step <STEP NAME> as requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when a sequence is started at a particular step.

This event always appears in the Event Summary.

No response required.

Action sequence <RECORD NAME> is already stopped. Ignoring Stop command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when a Stop command is issued to a sequence that is already stopped.

No response required.

Unable to start the action sequence at the specified step <STARTING STEP NAME> <USER AND SYSTEM NAME>. Could not find a sequence step record with that slot number.

This event is displayed when the action sequence is unable to start at the specified step because a sequence step record could not be found with that slot number.

Contact your Administrator.

Failed to load action sequence <RECORD NAME>. Ignoring Start command requested by <USER NAME> at <COMPUTER NAME>.

This alarm is displayed when the action sequence fails to load. This can be seen even when the resume command is issued.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

This is usually the result of a situation where two or more processes are trying to access the actionSequence record at the same time. This is temporary, and you should be successful when a second attempt is made. If this is not the case, contact your Administrator, who may need to review the log file to see what went wrong.

Action sequence <RECORD NAME> is already executing. Ignoring Start command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when the action sequence is already running. As a result, the system has elected to ignore the start command that was issued.

Wait for the action sequence to finish executing, or stop the action sequence and start it again.

Action sequence <RECORD NAME> is inhibited. Ignoring Start command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when an inhibited action sequence start is called on an inhibited record.

Contact the Administrator and request that the action sequence be uninhibited.

Unable to start the action sequence at the specified step <STEP SLOT NUMBER> as requested by <USER NAME> at <COMPUTER NAME>. The target sequence step <STEP NAME> does not belong to the action sequence record.

This message is displayed when an attempt was made to start an action sequence at a particular step, but the step is not associated with the parent action sequence record. This situation is extremely rare, and would represent an instance of serious misconfiguration.

This message is both Alarm and Event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

Contact your Administrator, who may need to contact AVEVA.

Action sequence paused as requested by <USER NAME> at <COMPUTER NAME> at step <STEP NAME>.

This event is displayed in the Event Summary when an action sequence step has successfully been paused.

No response required.

Sequence execution interrupted due to a fail-over or mode-switch.

This message is displayed when the sequence is stopped due to a system failure.

This message is both Alarm and Event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

Contact your Administrator.

Sequence execution interrupted at step <STEP NAME> due to a fail-over or mode-switch.

This message is displayed when the sequence is stopped due to a system failure.

This message is both Alarm and Event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

Contact your Administrator.

Step <STEP NAME> failed.No failure step exists for step. Terminating action sequence.

This event is displayed when the sequence is terminated because a step does not have a failure path.

Contact your Administrator.

Action sequence failed to pause as requested by <USER NAME> at <COMPUTER NAME> at step <STEP NAME>. The executing step failed. Action sequence <RECORD NAME> is now stopped.

This message is displayed when a Pause command issued on an executing step fails. If the action sequence cannot be paused, it will be marked as Failed.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

Contact your Administrator.

Failed to resume action sequence <RECORD NAME> as requested by <USER NAME> at <COMPUTER NAME>. Could not find a valid step to resume.

This message is displayed when resume fails because the paused action sequence does not have any idle or completed steps. This is a rare case and might occur in case of data inconsistency.

This message is both alarm and event. As long as the Administrator has not elected to inhibit the alarm and event messages, the alarms will appear in the Alarm Summary and the events will appear in the Event Summary.

You can attempt to manually force the start using Start at Step.

Action sequence <RECORD NAME> is not paused. Ignoring Resume command requested by <NAME> at <COMPUTER NAME>.

This event is displayed when a Resume is requested for an action sequence that is not in a Pausing or Paused state.

No response required.

Action sequence <RECORD NAME> resumed at step <STEP NAME> as requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when the action sequence is resumed from a paused state.

No response required.

Action sequence <RECORD NAME> is already running. Ignoring Resume command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when a Resume is requested for an action sequence that is already in an Executing state.

No response required.

Action sequence <RECORD NAME> is not executing. Ignoring Pause command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when a Pause is requested for an action sequence that is not in an Executing state.

No response required.

Action sequence <RECORD NAME> resumed as requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when an action sequence resumes an Executing state.

No response required.

Action sequence <RECORD NAME> pausing as requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed when you have clicked Pause. Since pausing could take a minute or two, depending on the complexity of the item being paused, an entry is created in the Event Summary.

No response required.

Action sequence <RECORD NAME> armed as requested by <USER NAME> at <COMPUTER NAME>.

This alarm is displayed when an action sequence is armed. This message is both alarm and event.

No response required.

Action sequence <RECORD NAME> does not have two-stage activation enabled. Ignoring Arm command.

This event is displayed if the action sequence receives an Arm command but has not been configured for two-stage activation.

No response required.

Action sequence <RECORD NAME> disarmed as requested by <USER NAME> at <COMPUTER NAME>.

This alarm is displayed when an action sequence is disarmed. If there is still an armed alarm present for the action sequence record that hasn't been acknowledged, this alarm will replace that one. This message is both an alarm and event.

No response required.

Action sequence <RECORD NAME> is not armed. Ignoring Disarm command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed in the event that the action sequence record has received a Disarm command when it was not currently in an Armed state. Alternatively, the action sequence record may be inhibited.

The action sequence may have been disarmed by another Controller. If it is inhibited, contact the Administrator and request that the action sequence be uninhibited.

Action sequence <RECORD NAME> is not armed, but received a Start command. Bypassing arming stage and allowing execution to continue.

This event is displayed when an action sequence that has two-stage activation enabled receives a Start command. The Action Sequence easy eXtended Operator Station (ezXOS) displays prevents you from starting an action sequence configured for two-stage activation without first arming it. However, other applications may need to start action sequences, while electing to bypass the two-stage activation process. The system allows such Start requests to bypass the arming stage and start the action sequence immediately. This warning event is provided to identify when this occurs.

No response required.

Action sequence <RECORD NAME> is <State>. Ignoring Arm command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed if the action sequence receives an Arm command but the command cannot be issued because it is in a conflicting state. An Arm command cannot be issued when the action sequence is in one of the following states:

• Executing

• Pausing

• Paused

• Inhibited

• Armed

Wait for the action sequence to finish executing, or stop the action sequence. If it is inhibited, contact the Administrator and request that the action sequence be uninhibited.

Action sequence <RECORD NAME> is already <RECORD STATE>. Ignoring <COMMAND> command requested by <USER NAME> at <COMPUTER NAME>.

This event is displayed if the action sequence receives a command but the command cannot be issued because it is already executing.

Wait for the action sequence to finish executing, or stop the action sequence.

Issued command <COMMAND> by <USER NAME> at <HOST>.

This event is displayed when a command is issued.

No response required.

Decision Step <STEP NAME> with a timeout of <TIMEOUT VALUE> second(s) has evaluated to false. Waiting for timeout to expire after an additional <TIME TO TIMEOUT VALUE> second(s) or a target result of true before proceeding.

This event is displayed when a Decision Step has evaluated to false but the timeout interval associated with the step has not expired.

No response required.

Decision Step <STEP NAME> with a timeout of 0 second(s) has evaluated to false. Waiting indefinitely for the Decision Step to evaluate to true before proceeding.

This event is displayed when a Decision Step has evaluated to false and the timeout interval associated with the step has been configured to 0 (for example, indefinite wait).

No response required.

Decision Step <STEP NAME> has evaluated to true. If a step is linked to this result, it will be executed next.

This event is displayed when a Decision Step has evaluated to true.

No response required.

Decision Step <STEP NAME> with a timeout of <TIMEOUT VALUE> second(s) has evaluated to false, and timeout has expired. If a step is linked to this result, it will be executed next.

This event is displayed when a Decision Step has evaluated to false and the timeout interval associated with the step has expired.

No response required.

Decision Step <STEP NAME> has evaluated to false. If a step is linked to this result, it will be executed next.

This event is displayed when a Decision Step has evaluated to false.

No response required.

Decision Step <STEP NAME> with a timeout of <TIMEOUT VALUE> second(s) has evaluated to true. If a step is linked to this result, it will be executed next.

This event is displayed when a Decision Step with an associated timeout interval has evaluated to true.

No response required.

Executing legacy action sequence <RECORD NAME>. This action sequence should be upgraded. Please contact your administrator.

This event is displayed when a legacy Action Sequence is executed.

The Action Sequence may need to be migrated. Contact the Administrator for more information.