...
...
...
...
| Excerpt |
|---|
The Workflow Monitor controls workflow execution and presents a detailed view of the workflow execution status. |
...
To open the monitor from the Execution Manager, see the section The Right-Click Menu, in the Execution Manager.
| Anchor | ||||
|---|---|---|---|---|
|
...
| Note |
|---|
Note!When you Enable Debug, it may slow down the workflow due to logging, especially if you set it to log debug into files in the workflow properties. For more regarding debug in workflow properties, refer to Debug Type in the Execution Tab. |
The following steps must be taken in order to view these events.
...
All running workflows are monitored by the workflow server on the Platform. A workflow can be in any one of the following states:
...
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 the Building state. When a workflow is in the Building state, in the worklow monitor, the text "Workflow is building" is also 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 the workflow is not running, 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 may 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 https://infozone.atlassian.net/wiki/spaces/MD92/pages/111805975/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 changes 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 the Scheduling section in https://infozone.atlassian.net/wiki/pages/resumedraft.action?draftId=23365112 . | ||||||||
Locked | Locked state is a special case that is only relevant when a batch workflow is present in multiple versions. That is, there are multiple workflows with the same name and instance id from the same workflow configuration. These can be in different versions of a package or be the same as a workflow outside any package. This means that in case of same workflows, the packages that these workflows are part of are ignored when considering whether they are different versions of the same workflow. If this is the case (and again, only for batch workflows), then only one version is allowed to run at a time. When one version of the workflow starts, the other ones enter into the locked state until the started one completes its execution. Only then is the next version allowed to start. This allows for collection using the file sequence number service to stay consistent even if the workflow version is updated. |
| Anchor | ||||
|---|---|---|---|---|
|
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 can be used in each state, see Analysis Agent.
Real-time agents only have three different execution states, that occur at every execution of the workflow.
...
The batch agents are more complex and contain additional states in order to guarantee transaction safety.
...
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.
...
An agent can have one of the following states:
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.
...
To be able to dynamically update TCP/IP Host and Port parameters, you need to set them to either Default or Per Workflow in the Workflow Properties dialog. See the figure The Workflow Table Tab in Workflow Table Tab.
To update, click Dynamic Update. On the bottom left of the workflow monitor, the text Dynamic Update followed by a number appears. It represents the number of times that you have updated the workflow configuration while running it, that is, since the last time you started it.
...
After a run the Download debug filesbutton is enabled and once you click on the button, the following dialog appears.
