Handling Operator Tasks Unexpected Conditions
Operator Tasks Error Message
The following section describes how to handle the Operator Tasks common error conditions.
Message/Issue | Situation | Do the following... |
The wanted task is missing in the Add list, in the Tasks tab. | You are creating a new operator task, and when you click Add the wanted task is not available in the list. |
|
| You have no authorizations to send commands belonging to a certain command group specified in the template. |
|
| You have no authorizations to send a certain set of event commands. | |
| You have no authorizations to view a certain property. | |
| You have no authorizations to access certain properties or commands. | |
| The access rights cannot be read. |
|
| The command is currently disabled. |
|
| A system component (for example, a driver) is not running. |
|
| A system component (for example, a driver) did not respond within a certain timeout. |
|
| The template contains invalid parameters. |
|
| One or multiple parameters are missing in the template. | |
| One or multiple parameters have out of range values. | |
| One or multiple parameters have wrong type values. | |
| The property does not exist. | |
| The alias does not exist. | |
| The template contains:
Or
| |
| ||
| ||
| Any other error different from what described for the errors above. |
|
|
Tasks Status Affected by Project Restart
If for any reason the project is to be stopped and restarted, this action will affect the tasks status as follows:
Before Project Restart | After Project Restart |
| The task status remains unchanged. |
| The task remains in this status and a check of the preconditions is done again. If the operator who started the task is no longer valid or the validation profile requires the operator’s input, the task status becomes |
| The task remains in this status, and the commands are executed again. If the operator who started the task is no longer valid or the validation profile requires the operator’s input, the task status changes to |
| If the task expiration time is not elapsed, the task remains in this status following the standard workflow (that is, until the task expires, or a command is executed on the task). If the task expiration time has elapsed:
|
| The task remains in this status and the revert commands are executed again. If the operator who executed the revert command is no longer valid or the validation profile requires the operator’s input, the revert command is not re-executed, and the task immediately starts to wait for conditions. |
| If the maximum timeout to wait for the conditions is elapsed, the conditions are checked immediately, otherwise the task starts to wait for conditions, following the standard workflow. |
| The task status becomes |