Automation rule lifecycle

The Lifecycle

Transitions Explained

Publication freezes the draft and selects it for later events. Subsequent edits create another draft without changing the current publication. Administrators pause or restore new event work, retire rules for history and delete only never-published configuration.

What Cannot Happen

Publication is the path from unpublished configuration to usable automation. Retired rules cannot be enabled again. Deletion is limited to never-published rules; published ones are retired instead.

Concurrency and Timing

Publication locks both rule and draft. Database checks permit one draft and protect published content from changes. Hosts read applicable publications at event time; disabling a rule does not cancel runs already raised.