Billing run action outcome

The Lifecycle

Transitions Explained

Each action starts planned and settles into an outcome. Done confirms its requested effect; skipped records that current facts need no work. Stale protects the reviewed term version, while failed records a supported refusal.

What Cannot Happen

Settled rows have no normal reset to planned. Executing the same run again skips those outcomes rather than repeating their effects.

Concurrency and Timing

Notice and drop settle in their database transaction. Order preparation checks under lock, then placement runs outside that transaction and settlement follows; duplicate prevention relies on the stable Commerce order key.