Allow User Abort and script cancellation control
ExpertControl whether users can cancel a running script with Escape, and communicate progress so they do not feel locked out.
What you'll learn
- When to use Allow User Abort [ Off ] vs. leaving it on
- How to show live progress so users know the script is running
- How to guarantee Allow User Abort is re-enabled even if the script fails
Allow User Abort [ Off ] prevents the user from pressing Escape to cancel a running script. This is appropriate for scripts that must complete atomically — mid-import, multi-record commits, external integrations — but requires that you communicate progress, since the user is effectively locked out of the interface.
1/3
1
Use Allow User Abort sparingly
Only disable user abort for scripts where a partial completion would leave data in an inconsistent state — bulk imports, multi-table updates, or API calls that must complete fully. For interactive operations, leave it on so users can escape.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo