Snapshot the approved version
Every scheduled destination references an immutable content snapshot so later draft edits cannot alter what was approved.
Turn approved content into durable publishing jobs with immutable snapshots, retries and visible failure states.
Start with ZenvikEvery scheduled destination references an immutable content snapshot so later draft edits cannot alter what was approved.
Provider failures can move through controlled retry states with attempt limits and backoff rather than creating duplicate posts.
In-app notifications and job states tell operators what succeeded, what is waiting and what needs intervention.
Publishing jobs use durable database identities and provider result tracking. Adapters are expected to use idempotent behavior where the destination supports it.
Material edits invalidate approval, and scheduled work references the immutable version that was approved.