THE TAKEAWAYS

What to take away

  • Cancellation has several boundaries
  • Clean up temporary state
  • Test immediate resubmission

EDITORIAL PRACTICE

Cancellation has several boundaries

Microsoft documents the cooperative cancellation model used by .NET. Closing a screen, notifying an application task and stopping a provider request are separate events. Explain the boundary that the actual stack supports rather than promising that every external task can be stopped.

EDITORIAL PRACTICE

Clean up temporary state

List temporary files, partial results, locks and pending records. Assign cleanup for both completion and cancellation. Keep saved results distinct from unsaved work so a cancelled task cannot remove a confirmed output, and follow the runtime’s cancellation conventions.

EDITORIAL PRACTICE

Test immediate resubmission

Cancel shortly after acceptance, during an external wait and just before saving. Then try the request again. Decide whether to reuse an identifier or create new work. Inspect uncertain external sends instead of assuming they were never executed.

EDITORIAL PRACTICE

Document recovery after interruption

Keep the last confirmed step separate from unresolved work. Define retention, cleanup retry and user-contact conditions. Verify the selected language and provider documentation because cancellation guarantees vary across stacks.

EDITORIAL PRACTICE

Distinguish old and new output

If a user restarts a cancelled PDF task, avoid mixing the previous temporary file with the new result. Check the recorded state before displaying success or failure. Include cancellation in acceptance checks reviewed by someone other than the implementer.

WITH OPERUN.

Delegate everyday AI management.

Use the documented mechanism as a starting point, then verify the real workflow, its limits and its recovery conditions. A useful handover connects the expected behavior with evidence that another operator can reproduce.

Discuss your product and AI work

Primary sources

Sources checked on 6 November 2026. The workflows and checklists are editorial proposals.

  1. [1]

Share this insight