Orchestration Workflows

The Orchestration Workflows sub-tab displays additional details if an event matches an orchestration workflow.

Event processing can fail for the following reasons:

The Orchestration Workflows tab reports on the success or failure of the event and its orchestration workflows.

Note: If the event status is Received, the table will be empty because either no orchestration workflows are mapped to the event, or the orchestration workflows mapped to the event could not be created.
Field Description
Name The name of the orchestration workflow that was triggered by the event.
Status The status of the orchestration workflow processing:

Created: The workflow has not been invoked yet; no processing data has been found.

Transmitted: The workflow has been placed in the first queue of the processing pipeline.

Pending: The workflow has been placed in the second queue of the processing pipeline.

Started: The workflow was invoked.

Success: The workflow was processed with no exceptions.

Failure: Exceptions occurred during the workflow processing.

Last Processed On The date and time the last attempt was made.
Attempts The number of times the Event Manager tried to match the event to an orchestration workflow. Currently, this value is always "1."

Logs from the orchestration workflow associated with this event appear to the right. Each orchestration workflow instance that runs from the event should log at least a [BEGIN] message and an [END] message. The [END] message indicates if the orchestration workflow succeeded or failed. A success is indicated with an [OK] message. A failure is indicated by an ERROR message and the text of the exception or SOAP fault that occurred. The text of the SOAP fault is always captured; for certain types of SOAP faults, the message text is also extracted. The message text is truncated if it is over a certain size.

Click Display message to view the entire contents of the message.