Inspect or cancel a Python workflow

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.
• {{workflow_id}} Exact caller-owned workflow ID.
• {{action}} Inspect or cancel.

Prompt

Use read_v2_python_program_workflow for {{workflow_id}} in {{workspace_id}} / {{application_id}}.
Report status, child jobs and committed receipts.
For {{action}} inspect, stop there.
For cancel, verify the target and authority, call cancel_v2_python_program_workflow, and read the resulting status.
Report which units had already committed and which work stopped.
Stop on scope mismatch or access failure.

Example inputs

Start with action set to inspect on the workflow from the disposable sealed-plan run. To exercise cancellation, start a separate workflow with its own request key from a reviewed build in a disposable application. Use an empty target and cancel while work is pending. Read the final state and checkpoints. A cancellation before the first commit leaves the target cell empty and reports zero committed units. A unit that already committed retains its receipt and effect.

Tools used include read_v2_python_program_workflow, cancel_v2_python_program_workflow. See the module guidelines and tool index.