Recurring billing run schedule

The Lifecycle

Transitions Explained

The active flag controls whether delivered occurrences create work. Pause and resume update the underlying schedule, while rescheduling changes its rule. An occurrence reuses its existing batch and continues only unfinished stages.

What Cannot Happen

A paused occurrence returns a skipped answer. Pausing an already paused configuration is not a forbidden lifecycle transition; version checks still apply.

Concurrency and Timing

Occurrences use the configured customer time zone. Recurring updates lock and version-check the configuration, and occurrence uniqueness protects batch creation.