Excerpt |
---|
The Workflow Monitor controls workflow execution and presents a detailed view of the workflow execution status. |
...
State | Description | ||
---|---|---|---|
| The | ||
| This state is only applicable for batch workflows. At every start of a new batch, the batch collection agent emits a | ||
| The agents 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 calls for the | ||
| This state is only applicable for batch workflows. Once the batch is successfully processed or sent to the 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 enter the |
Viewing Abort Reasons
In most cases if a workflow has aborted, one of its agents has a red square outline surrounding it. Double-clicking such an agent displays the Agent Status dialog with 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 workflows. |
Running | The agent has received data and is executing. For agents that are running, there is a green square outline surrounding them. |
Stopped | The agent has successfully finished processing data. |
Aborted | The agent has terminated erroneously. For an agent that is aborted, there is 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 allow parts of them to be reconfigured while active. When double-clicking the agent in monitor mode, the agent's configuration is shown 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.
...
The transaction model is based on the premises that collection agents are free to initiate a transaction to the transaction server. At the moment the complete workflow is frozen and the transaction server saves the state of the workflow data that is queued for each agent. In practice, agents indirectly emit a transaction when an End Batch is propagated. When all data is secured, the workflow continues the execution.
Debug
A workflow can be configured to send debug logs as an event or to a file. When an event is selected, the debug logs will be present in the text areas in Workflow Monitor View.
...
When the Debug Type is File, the debug will be written to a file in MZHOME of the Execution context. The default file location is in a debug directory inside the temporary directory decided by this property pico.tmpdir
. It can also be set directly using this property, mz.wf.debugdir
.
When the debug is sent to a file, an additional button will be visible in the Workflow Monitor, Download debug files.
...
After a run the Download debug filesbutton is enabled and once you click on the button, the following dialog appears.