Retry & cancel

What this is

Retry and cancel are the two ways to act on a post that hasn’t published yet. The confirm: true gate is an MCP thing, not a REST thing for these two: dropslate_retry_post and dropslate_cancel_post both refuse without it, but POST /posts/:id/retry and /cancel take no request body at all and act the moment they’re called - the confirmation step for a human is whatever the dashboard’s own click-through UI does before it sends that call, not something the route itself enforces. The one place REST does enforce it server-side is creating posts - see Publish your first post and CLAUDE.md’s “plan before create.”

Retry

Only a failed post can be retried. It is sent to the network again - at its original time if that is still ahead, otherwise immediately. Retrying does not create a new post; the same post moves back to queued (then live or failed again, from the same send).

Cancel

Only a queued post can be cancelled. It moves back to draft, off the queue - nothing is deleted, and it can be scheduled again later.

Reschedule

Move a queued post to a new time, or give a draft a time for the first time (which queues it). PATCH /posts/:id takes no confirm field either (it’s a .strict() schema - sending one is rejected as an unrecognised field); dropslate_reschedule_post still requires confirm: true.

Common errors

Error	Cause	Fix
confirm_required (MCP only)	Called dropslate_create_post, dropslate_retry_post, dropslate_cancel_post or dropslate_reschedule_post without confirm: true.	Reissue the call with confirm: true.
confirm_required (REST, POST /posts only)	Created a post without confirm: true in the body.	Send the same body again with confirm: true.
Retry refused on a live or draft post	Only a failed post can be retried.	Nothing to do - a live post already sent; a draft has no send to retry, schedule it instead.
Cancel refused on a draft, live or failed post	Only a queued post can be cancelled.	Nothing to do for draft or live; a failed post is retried, not cancelled.