A resumed node runs again, and so do its side effects.

Larkspur Cloud’s refund graph triages a request, assesses risk, waits for the billing team when the risk is high, then calls the payment provider. Pick a request, a fault in the provider call and whether the two guards are on. The log shows every client call, what the updates stream yielded and what reached the outside world.

Refund request

Fault in execute

Guards

On: the approval notice gets its own node before the gate, and the refund call carries an idempotency key.

Client calls
Checkpoints
Approval notices
Refunds issued

The run, call by call

Thread

From	What happened

Recorded from LangGraph 1.2.18 running this graph with InMemorySaver. The nodes are stubs modelled on the refund agent in the 06a notebook; the provider is a stand-in that fails the way the fault says.

Checkpoint history

Oldest first

Step	Next node