AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Agents

Time-Delayed Execution

Insert a cancelable countdown before a high-impact action runs. Give a last chance to stop sends, spends, deletes, or external side effects.

Interactive demo

Send email

Invoice follow-up

To billing@acme.example · you can cancel for a few seconds after sending.

Q2 invoice reminder

billing@acme.example · attached PDF

Overview

How might we design time-delayed execution so people can trust and act on AI output?

When to use

  • Essential for email clients, payment flows, agent actions, and any interface where high-impact irreversible operations benefit from a short cancelable window.

When to skip

  • Low-stakes local edits where delay only frustrates.
  • Emergency stop systems that must act immediately.
  • Actions already gated by a full approval review with no time pressure.

Rules

  • Delays too short to read the payload.

  • No visible countdown or cancel control.

  • Continuing the action after the user hit cancel.

  • Using delay as the only safety net for irreversible ops.

Evidence

ProductImplementation
GmailUndo Send window after sending mail.
SlackScheduled send and editable pending messages.
CursorConfirm windows before risky agent-applied changes.
StripePayment confirmation steps before capture.

FAQ

What is time-delayed execution?

It is a short cancelable wait between confirming an AI action and the side effect landing, similar to Undo Send.

How long should the delay be?

Often 5–30 seconds for messages; longer for deletes or spends. Match the time needed to skim the payload.

How does it differ from human-in-the-loop?

HITL requires explicit approval. Time delay assumes intent but still allows abort. Many flows use approval first, then a short undo window.

What must the countdown UI show?

What will happen, when, and a prominent Cancel. Optional Edit beats forcing a full restart after cancel.