What cancelling an AI workflow should mean
Cancellation is a request to stop work. It is not automatically a rollback of records already written or a reversal of external actions already completed.
Define the boundary of cancellation
For a batch of one hundred records, some may have finished before cancellation arrives. Decide what your application shows for completed, pending, and interrupted rows. A model call already in flight and a queued record may stop differently. If the workflow writes to another service, define whether compensating actions are available and whether a person must approve them.
- 1Keep the run ID and submit cancellation…Keep the run ID and submit cancellation through its supported API.
- 2Read the eventual terminal status and row…Read the eventual terminal status and row outcomes.
- 3Review completed destination writes before considering any…Review completed destination writes before considering any cleanup.
Try it on a small example
- Keep the run ID and submit cancellation through its supported API.
- Read the eventual terminal status and row outcomes.
- Review completed destination writes before considering any cleanup.
What to verify
In Baleybots, run status and counters are controlled by database operations, including cancellation. Inspect the resulting run instead of predicting its state solely from the cancellation request's response. Test cancellation on a small run that is waiting for approval and another that is actively processing. Your client should distinguish requested cancellation from observed completion, and should never label existing external writes undone without verifying them.
Product details checked against the Pipeline architecture on October 4, 2026. These guides describe documented behavior; availability depends on your account and the deployed service. Baleybots is in invite-only beta.