Open your integration and choose Delivery history. Each result belongs to a delivery to that connection.
What the results mean
- Waiting: the article is queued for delivery.
- Sending: delivery is in progress.
- Sent or accepted: the destination accepted the article, but a public page has not been confirmed.
- Saved as draft: no public URL was reported. Check the CMS entry; this label alone does not prove its draft state.
- Sent to Zapier: Zapier received the message. Check Zap history for later actions.
- Sent to Notion: a Notion page was saved. It may still be private.
- Published: the integration reported publication. Check the actual page for its appearance and visibility.
- Needs attention: delivery failed. Read the details and fix the connection or destination.
The exact labels vary by integration.
Retry a failed delivery
First check the destination for the article. A request can succeed there even if the response did not reach Spron.
Fix the cause, then use Retry delivery where it is available. Your receiver or Zap should recognise the article ID and update the existing post.
Temporary failures may also be retried automatically. Repeatedly pressing retry does not make a missing permission or broken field mapping work.
Check a missing page
Where available, Check destination checks stored public page URLs. It can detect missing pages, but it does not compare the full article or prove that search engines have indexed it.
Zapier has no Check destination action because Spron does not know whether the later Zap steps published a page.
See An article did not arrive for the next checks.