A caller saying “wait, use the other address” changes the requested action, but it may arrive after execution has started. Cancellation needs a state-aware backend response, not just a new instruction in conversation memory.
Pending actions have different cancellation windows
Cancelling a pending action means preventing a not-yet-committed operation from executing, or reconciling its outcome if it has crossed the commit boundary. Queued, running, committed, and uncertain operations need different treatment.
In a proposed workflow, each confirmed intent has a revision number. An action carries the revision it was created from. A correction advances the revision and invalidates earlier work that has not committed. The execution service checks the current revision at a defined checkpoint before writing.
That check alone cannot stop a remote write already in progress. Where the destination provides cancellation, use its documented mechanism. Otherwise reconcile the result and decide whether a separate corrective operation is possible and authorised.
Work through a fictional address correction
A caller confirms a service request for 12 River Road. The assistant queues the save, then hears “sorry, number 21.” If the job has not begun, the system can cancel the old revision and prepare a fresh confirmation for 21 River Road.
If the first save already completed, the system should identify the saved request and apply the supported amendment process. It must not tell the caller the original request was never saved. If execution status is unknown, say that the update is being checked before making a definitive promise.
| Correction timing | Expected result |
|---|---|
| Before confirmation | Update the draft only |
| After queueing, before execution | Invalidate the old revision |
| During remote execution | Reconcile before retrying or amending |
| After confirmed commit | Use a separate authorised correction |
Inject the correction at each boundary in a deterministic test. Inspect both the action ledger and the resulting business record. Hearing the corrected address in the final response does not prove the stored address changed.
Cancellation should not erase evidence
Retain the original operation reference, cancellation request, and final disposition. Staff need to distinguish an action that never executed from one that executed and was later amended. Avoid storing unnecessary sensitive conversation content in that ledger.
A central revision check adds coordination and can reject legitimate work when updates arrive quickly. That is preferable to writing superseded details, but the assistant needs a clear recovery response rather than an unexplained failure.
The HVAC request case study demonstrates caller confirmation before saving; the revision-based cancellation mechanism here is proposed. See stale-state prevention for the related concurrency problem.
Pending action FAQ
Does interrupting speech cancel a tool call?
No. Speech interruption and business-operation cancellation are separate events.
Can a committed action always be undone?
No. Some effects require compensation, staff review, or cannot be reversed.
What should the caller hear during uncertainty?
Explain that the original action’s status is being checked and avoid confirming either cancellation or completion without evidence.