pydo.harness.cancel_trigger_execution()
Generated on 16 Oct 2026
from pydo version
v0.44.0
Usage
client.harness.cancel_trigger_execution(
trigger_id="b1a0c6de-1f2e-4a3b-9c8d-0e1f2a3b4c5d",
execution_id="7c1f9e2a-3b4c-5d6e-7f80-91a2b3c4d5e6",
force=None,
)Description
Fails the execution and frees the trigger’s in-flight slot. A fresh-mode session is destroyed outright. A reuse-mode session is only paused, not stopped - harness has no run-interrupt call, so the agent’s turn may still be in flight server-side; this frees the queue, not necessarily the agent’s work. A non-running execution is a no-op that still returns 200.
Parameters
trigger_idstring requiredExample:
b1a0c6de-1f2e-4a3b-9c8d-0e1f2a3b4c5dThe trigger UUID.
execution_idstring requiredExample:
7c1f9e2a-3b4c-5d6e-7f80-91a2b3c4d5e6The execution UUID.
forceboolean optionalExample:
FalseCancel even if the execution has not started a run yet (the worker's own dispatch may still be in flight). Without this, that case returns 409; reclaim clears it automatically within 15m regardless.
Response Example
More Information
See /v2/agents/triggers/{trigger_id}/executions/{execution_id}/cancel in the API reference for additional detail on responses, headers, parameters, and more.