The outcome

Ensure consequential actions cannot run until a reviewer approves or safely edits their exact arguments.

Step by step

A workflow you can repeat.

  1. 01

    Place the interrupt immediately before the side effect and construct a review payload with action, arguments, impact, and source context.

  2. 02

    Persist the graph with a production checkpointer and bind each execution to authenticated user, tenant, and thread identifiers.

  3. 03

    Allow explicit approve, edit, or reject outcomes and validate edited arguments again before the action node runs.

  4. 04

    Test delayed review, rejection, duplicate decisions, expired authorization, process failure, replay, and attempted cross-thread access.

  5. 05

    Record the reviewer and decision separately from sensitive state, monitor pending interrupts, and rehearse recovery from the last checkpoint.

Working standard

What good use looks like.

  • Interrupt before the effect.
  • Revalidate edited arguments.
  • Prevent cross-tenant state access.

Official references

Check the current product documentation.