agent-team-task-cancel

To cancel a non-terminal task in workflow orchestration, provide the task ID and a rationale. The system validates the required fields, ensures the task is not terminal, and emits a cancellation event to update the run history.

Recording a rationale when aborting an agent-team task prevents wasted work and misaligned states across runs. The cancellation event logs the decision to keep workflows consistent during scope changes or prioritization shifts.

You cannot cancel a task that is already in a terminal state. The cancellation process validates the target task and ensures it is non-terminal before processing the cancellation event and updating the event log.

The best way to prevent cascading delays during a workflow run is to abort non-terminal tasks causing the bottleneck. Cancelling the task with a clear rationale stops wasted work and updates the run history immediately.

Cancelling a task updates the event log automatically. The system validates the task ID and reason, confirms the task is non-terminal, and emits a cancellation event to reflect the decision in the run history.

You need to cancel a non-terminal task in state management when a task must be aborted to prevent wasted work or cascading delays throughout a run, often due to scope changes or prioritization shifts.