Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Monitoring a workflow does not imply exclusive rights to start or stop it, the workflow can be activated and deactivated by another user while monitored, or by scheduling.

Viewing Agent Events

While a workflow is running, agents report progress in terms of events. These events can be monitored in the event area at the bottom of the window. The following steps must be taken in order to view these events.
 

  1. To view events for all agents in the workflow, select Events for All Agents from the Event menu.
     

  2. To only view events for some selected agents, click each agent while holding down the <Ctrl> key on the keyboard.

    1. Select Events for Selected Agents from the Event menu.

    2. If required, rearrange the size and position of each column.

Excerpt
hiddentrue

Workflow States

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

Aborted

At least one of the workflow agents has aborted. You can track the reason for the error from the stack trace available from the monitor or by examining the System Log.

Building

When a workflow, or any of a workflow's referenced configurations, is being re-built, for example when saving or recompiling, the workflow is in Building state.

When a workflow is in Building state, the Configuration Monitor icon in the status bar indicates that operations are in progress, and in the Workflow 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.

CompletedA workflow with the state completed is one that has successfully run without hitting any other states listed in the table.

Hold

A workflow that is in the Idle state and is being imported either by the mzcli systemimport r | sr | sir | wr or by the System Importer configured to Hold Execution, enters the Hold state until the import activity is finished. The Workflow group then resumes its Idle state.

Idle

Until you execute the workflow for the first time it is in the Idle state. After execution, although the workflow is indeed idle, the state space on the display might remain as any of the following states: Executed, Completed, Aborted, or Not Started.

Invalid

The workflow configuration is erroneous. Once you correct the error, the workflow assumes the Idle state. Note: A workflow in the Invalid state cannot be executed.

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.

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.



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 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.

Anchor
transactions
transactions
Transactions

A workflow operates on a data stream and Usage Engine 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.

...