post.scheduled only fired on creation before, so queueing never notified you. It now fires whenever a post enters the scheduled state: created with a schedule, added to a queue, promoted from draft, retried after failing, or created as a recycled clone. Editing or rescheduling an already-scheduled post does not fire it.
Since a post can now emit it more than once (queued, later retried), key your handler on the post id so repeats are idempotent.
Log in to comment and vote
Comments1
Aug 6
PinnedShipped, live now.
post.scheduled only fired on creation before, so queueing never notified you. It now fires whenever a post enters the scheduled state: created with a schedule, added to a queue, promoted from draft, retried after failing, or created as a recycled clone. Editing or rescheduling an already-scheduled post does not fire it.
Since a post can now emit it more than once (queued, later retried), key your handler on the post id so repeats are idempotent.
Docs: https://docs.zernio.com/webhooks/posts
Thanks for flagging it.