Observed

interrupt()/Command(resume) is confirmed as the working primary mechanism, with production constraints that fail silently rather than loudly: a node containing two interrupt() calls leaves get_state().next empty after the first resume — the graph is still paused but the snapshot reports it complete, so an approval gate can be silently skipped (#6956, opened 2026-02-27, open and re-verified 2026-06-11); interrupt call order must be deterministic; nodes re-execute from the beginning on resume (idempotency required); a bare try/except absorbs the interrupt exception and the graph never pauses. No built-in notification, timeout, or escalation exists — interrupted threads persist in the checkpointer indefinitely.