Guide

How should an AI agent handle a request cancelled during processing?

Scope request cancellation: pending actions, work already completed, confirmation of the stop, and a restart subject to fresh approval.

By AIKUB ·

A request was valid when the agent began processing it. The client then writes: “We no longer need that document.” Before continuing, the cancellation needs to be linked to the right case and the actions that can still be stopped need to be checked. This guide proposes a framework for distinguishing a stop request, a confirmed stop, and completed work, without promising that a completed action can be erased.

Which request needs to stop?

Define what identifies a cancellation instruction: the requester’s identity and authority, case reference, document involved, and scope of the stop. Cancelling document preparation does not mean closing the entire client case. If the message is ambiguous, define how affected actions should be placed on hold under agreed rules, then request human clarification.

In a fictional example, a professional services firm is preparing a document for a client. The client withdraws the request while the draft awaits approval. The expected result is to suspend that preparation and its dependent steps, not delete the client’s other requests. This is a scoping example, not a reported client result.

What should be checked in work already prepared?

List the steps linked to the request: draft, pending approval, scheduled task, and any sending step. For each, identify the tool involved, its verifiable state, and the person authorized to stop it. A note in the case record is not, by itself, confirmation that a pending task in another tool has been disabled.

Have the technical team define controls that prevent a pending step from starting after a recognized cancellation. Include the case where an approval arrives after the stop message. That earlier approval must not reactivate the request by default. What is possible depends on the connected tools and must be tested, not merely written into an instruction.

How should a partial stop be reported?

Separate what is confirmed stopped, what is already complete, and what has an unknown state. If a document has already been sent, do not describe the entire request as cancelled without consequence. Have the records checked in the authorized tool and tell the owner what actually happened. Completed work may require a separate follow-up rather than a reversal.

Keep the cancellation reference, affected steps, and useful confirmations in authorized tools. Do not automatically delete records or existing documents. Any corrective message, sharing withdrawal, or case change needs its own permissions and approvals. If the stop cannot be confirmed, say so clearly instead of reporting that everything is resolved.

Which scenarios should be tested before use?

Use anonymized data and keep tests separate from real sending. Test cancellation before preparation, during approval, after a completed step, and with an ambiguous reference. Add an approval received after cancellation and another active request for the same client. Verify that the right work stops and unrelated requests remain intact.

For each test, write down the expected states, evidence to inspect, and required human decision. If the client later changes their mind, treat restarting as a new decision with an explicit scope. Recheck the document, recipients, and relevant approvals; do not automatically put an old draft back into circulation simply because it still exists.

How can you prepare for an AIKUB diagnostic?

Bring an anonymized example of a withdrawn request, the steps it triggers, and the tools where their state can be checked. Identify who may request the stop, who confirms its effect, and who authorizes any restart. The first scope can be limited to recognizing cancellation and preparing a list of actions for a person to check.

AIKUB supports the scoping of personalized, governed agents, with support and training included. Find your first quick win in a repetitive computer-based task while also defining how it stops. The diagnostic helps specify boundaries and necessary controls before broader actions are delegated to the agent.

Frequently asked questions

Does cancellation erase work already completed?

No. Distinguish stopped steps from completed actions. Any corrective follow-up requires an appropriate decision and authorization; do not promise automatic reversal.

What if approval arrives after cancellation?

Late approval must not reactivate the request by default. Check its link to the case and have any restart confirmed against the new scope.

Should every request from the client be stopped?

No. Identify the request and its dependent steps. An ambiguous instruction needs clarification without automatically cancelling unrelated work.