Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

BAM Execution Reports

  • Last UpdatedOct 28, 2025
  • 3 minute read

BAM Execution Reports are used to monitor and analyze workflow execution in the selected repository. They provide visibility into the status of workflows across different stages.

Workflow Status Summary

This chart shows a summary of workflow statuses in the selected repository.

 


Workflow Status Types

The following status reports provide details of workflow execution:

Executing

This report presents details of workflows that are currently in execution.

Awaiting

This report shows details of workflows awaiting execution.


Completed 

This report shows details of workflows that have been successfully completed. In this view, no rows appear because there are no completed workflows to represent.

Failed 

This report shows details of workflows that failed during execution.

You can also view a consolidated report of all workflows executed with errors, as shown below:

Aborted

This report shows details of workflows that were aborted, as illustrated in the following image. Quickflows that completed with errors are also listed here instead of under Failed.

Paused

This report shows details of workflows that are currently paused.


WorkItem Transaction Details

This view provides a breakdown of workflow activities and their current status.

Limitations for Token-Based Repositories

In BAM Execution Reports, the Initiator column indicates who initiated the workflow.

  • Non-token-based repositories:

    If the actor in a Human Activity is set to Workflow Initiator, the user who executed the workflow or created the event is shown as the Initiator, and the corresponding work item is delivered to that user’s Inbox in the Enterprise Console.

  • Token-based repositories (such as AIM and Microsoft Entra):

    When workflows are scheduled or triggered by the workflow engine (not by a user), the Initiator column in BAM reports shows the client ID of the registered token service. Since no user is involved, no work item is delivered to any user’s Inbox for the following events:

    • Scheduler

    • File Watcher

    • BAM

    • ArchestrA Event

    • Message Queue

TitleResults for “How to create a CRG?”Also Available in