...
When a workflow is executed using workflow profiling, continuously samples the load, i e the amount of processed UDRs, or raw data, per second. The average load for a workflow is calculated on a regular basis and the status for all routes and agents will be determined based on the average.
...
State | Description | |||||||||||
Building | When a workflow, or any of a workflow's referenced configurations, are being re-built, for example when saving or recompiling, the workflow will be in Building state.
When a workflow is in Building state, the Configuration Monitor icon in the status bar will indicate that operations are in progress, and in the Worklow Monitor, the text Workflow is building will also be displayed. Workflows started by scheduling configurations will wait until the workflow leaves the Building state before they start. | |||||||||||
Executed | A Workflow becomes Executed after one of the following:
| |||||||||||
Hold | A workflow that is in the Idle state and is being imported either by the mzsh systemimport r | sr | sir | wr or by the | |||||||||||
Idle | A workflow is in Idle state if there is no activity going on in the workflow. It means that workflow is not running, or, not in process of starting or stopping or not in any other state (Invalid or Hold). After execution, although the workflow is indeed idle, the state space on the display might remain as one of the following states:
| |||||||||||
Invalid | The workflow configuration is erroneous. Once you correct the error, the workflow assumes the Idle state.
| |||||||||||
Loading | The platform is uploading the workflow to the Execution Context. When the transfer is complete, the Execution Context initializes the agents. When the workflow starts running the state changes to Running. | |||||||||||
Running | The workflow is currently executing. | |||||||||||
Unreachable | If the Platform fails to establish connection with the EC where a workflow is executing, the workflow enters the unreachable state. When the workflow server successfully reestablishes the connection, the workflow is marked as Running, Aborted, or Executed, depending on the state that the workflow is in. An Unreachable workflow may require manual intervention if the workflow is not running any more. For further information see Execution Context in Desktop User's Guide. | |||||||||||
Waiting | The Waiting state applies only to workflows that are included as members in a workflow group. In the Waiting state, the workflow cannot start execution due to two parameters in the workflow group configuration: The Startup Delay parameter, and the Max Simultaneous Running quota. A workflow in the Waiting state will change to Running when triggered either by a user, the scheduling criteria of its parent workflow group, or by a more distant ancestor's scheduling criteria. For further information see Scheduling. |
...
The workflow execution state provides granular information about a workflow's current execution status. In APL, there are function blocks that are called for each workflow execution state. For more information about which APL functions that may be used in each state, see 9.6 5 Analysis Agent.
Real-time agents only have three different execution states, that will occur at every execution of the workflow.
...
A workflow operates on a data stream and supplies and supplies a transaction model where persistent synchronization is made from the workflow data and agent-specific counters. In theory the synchronization could be performed continuously on a byte level, but in practice this would drastically decrease the performance of the system.
...