Excerpt |
---|
The Workflow Monitor controls workflow execution and presents a detailed view of the workflow execution status. |
Agent states and events can be monitored during workflow execution.
...
State | Description | |||||
---|---|---|---|---|---|---|
| The | |||||
| This state is only applicable for batch workflows. At every start of a new batch, the batch collection agent will emit a | |||||
| The agents will handle all incoming UDRs or bytearrays during the | |||||
| This state is only applicable for batch workflows. When all UDRs within a batch have been executed, the agents enter the | |||||
| This state is only applicable for batch workflows. The collection agent will call for the | |||||
| This state is only applicable for batch workflows. Once the batch is successfully processed or sent to ECS, the | |||||
| This is the last execution state for each workflow invocation. The agents clean and release resources, such as memory and ports, and stop execution. | |||||
| This state is only applicable for batch workflows. If an agent fails the processing of a batch it may emit a
| |||||
| This state is only applicable for batch workflows. If the last execution of the workflow aborted, the agents will enter the |
Viewing Abort Reasons
In most cases if a workflow has aborted, one of its agents will have a red square outline surrounding it. Double-clicking such an agent will display the Agent Status dialog containing the abort reason. The System Log also holds valid information for these cases.
...
State | Description |
---|---|
Created | The agent is starting up. No data may be received during this phase. This state only exists for a short while during workflow startup. |
Idle | The agent is started, awaiting data to process. This state is not available for a real-time workflow. |
Running | The agent has received data and is executing. For agents that are running, there will be a green square outline surrounding the agents. |
Stopped | The agent has successfully finished processing data. |
Aborted | The agent has terminated erroneously. For an agent that has aborted, there will be a red square outline surrounding the aborted agent. The error reason can be tracked either by double-clicking the agent or by examining the System Log. |
Agent Configuration
Some agents allows parts of them to be reconfigured while active. When double-clicking the agent in monitor mode, the agent's configuration is shown in the displayed dialog if the agent can be reconfigured. When the configuration has been updated it can be committed to the active workflow using the Dynamic Update button in the toolbar.
...