Inspect a workflow occurrence

Replace the placeholders with values from your own authorized scope before copying this prompt into an MCP client.

Inputs

• {{workspace_id}} Stable workspace ID.
• {{application_id}} Stable application ID.
• {{occurrence_id}} Exact occurrence ID from an authorized occurrence.

Prompt

In {{workspace_id}} / {{application_id}}, use read_v2_program with application.workflow.occurrence.read, occurrenceId {{occurrence_id}} and eventLimit 25.
Use nextEventOrdinal as afterEventOrdinal if another event page is needed.
Report flowId, version, definitionDigest, status, occurrenceVersion, activities and any visible evidence on the events. Identify which activities are Ready or Blocked.
Stop before completing, returning or cancelling an activity.
Stop with the access error if the occurrence cannot be read.

Example inputs

Start from the saved disposable workflow. As a separate authorized setup step, publish its exact flowId and version using application.workflow.publish and the current workflow state, metadata, policy and schema revisions. Read back the published workflow and refresh all four revisions. An administrator can then call execute_v2_application_workflow_occurrence with application.workflow.occurrence.start, the same flowId and version, the four expected revisions, and a new request key. Use the returned occurrenceId for the read-only prompt.

The new occurrence is Active. prepare is Ready and review is Blocked. The OccurrenceStarted event records the start. Activity evidence appears when an authorized transition attaches it.

Tools used include read_v2_program, execute_v2_application_workflow, and execute_v2_application_workflow_occurrence. See the module guidelines and tool index.