Two kinds of problems
Temporary problems - theStacc retries for you
The scheduled publishing worker retries failures classified as temporary. Its fast tier includes the first five attempts, with increasing waits and random jitter. If transient failures continue, a slow tier schedules further attempts after configured waits of 1 hour, 3 hours and 12 hours. Once those delays are exhausted, another transient failure is marked failed. Those waits are eligibility delays, not a completion window: scanning and queue timing can make a request run later. A successful request can end the retry sequence early; repeated failures can leave the blog in Publish Failed. A rate-limit response is a signal to slow down, not proof that waiting alone will resolve the issue. An action you trigger manually can instead return an error directly. Do not assume every failed Publish Now or Sync Changes request has been placed in the scheduled retry queue. Inspect the resulting status and message.Permanent problems - theStacc stops and tells you
The scheduled worker stops on failures classified as requiring a change, such as rejected credentials, insufficient permissions, or invalid content. Correct the cause before requesting another attempt. A new password does not fix an invalid CMS field, and a new slug does not fix a revoked token. Publishing URLs are also checked for allowed public destinations. A private or internal address can be rejected before content is sent. That check does not certify the receiver’s security or its ability to publish the payload.What a failure message tells you
An error message helps locate the failing step. Authentication messages point toward credentials or account access; validation messages point toward the submitted content or destination schema; a timeout leaves uncertainty about whether the receiver completed the request. The message is not a promise about internal incident handling, a complete diagnosis of every platform response, or proof that nothing was published. Record the blog, action, destination, and message when asking for help. Keep API keys, application passwords, and webhook secrets out of support screenshots or messages.New post vs. republish
For supported update paths, theStacc uses a stored external post ID to update an existing post. The current detail page offers Sync Changes for a published blog, Republish for an unpublished blog, and Retry Publish for a blog marked Publish Failed. A stored ID does not guarantee that the remote post still exists. Some connectors can recreate a post when the stored ID is stale. Inspect the destination before retrying, particularly if somebody deleted, moved, or edited the remote post outside theStacc. Webhook events can distinguish a new publication from an update, but the receiving application must implement the corresponding create or update behavior. See Webhook Reference for the integration contract.How theStacc avoids duplicate posts on retry
Some connectors check for a previously created post before repeating a request. Those checks differ by platform and depend on available identifiers and matching rules. They reduce duplicate risk; they do not establish a universal guarantee that every retry is duplicate-free. Before retrying a timeout or interrupted request:- Search the destination for the blog’s title and slug.
- Check whether an existing post is the intended article and whether its content is current.
- Inspect the stored live link or external ID when available.
- Resolve an uncertain match before repeatedly creating another post or changing its slug.
idempotency_key, while the manual path is not identical. Verify the payload for the path you use and implement stable duplicate handling at the receiver. HTTP does not make a repeated POST automatically idempotent; see the HTTP idempotency specification.
What the per-platform messages mean
WordPress
For a self-hosted WordPress connection using an Application Password, check the username, password, and site URL. An Application Password is separate from the user’s normal login password. WordPress documents creating it in the user’s profile and using it with REST API authentication over HTTPS; see WordPress REST API authentication. An authentication error does not establish that the password was the only cause. A permission error needs a check of the connected user’s capabilities and access to the affected post. For WordPress.com OAuth, reconnect the account when the connection reports invalid or expired authorization.Ghost
Check the Admin API key and admin URL associated with the Ghost integration. A Content API key is not a substitute for the credentials used to write through the Admin API. Ghost’s admin domain can differ from the public site’s domain; see Ghost Admin API documentation. For a validation error, read Ghost’s returned field or content explanation before replacing a working key.Zepio
Inspect the site URL and Developer API credentials configured in the integration when a Zepio request is rejected. If the scheduled request is rate-limited, check its retry status rather than issuing repeated manual requests. The current theStacc Zepio connector does not support republishing a post already associated with that connector. This describes the connector’s behavior, not a claim about every capability of Zepio’s current API. Check the post directly in Zepio before deciding how to correct it; deleting it is not a harmless prerequisite.Webflow
Check the token, site, collection, field configuration, and returned validation message. If a slug conflicts, inspect the existing CMS item before changing the article’s URL. A conflict does not prove that the existing item is unrelated. Check the public site as well as the CMS item. Webflow distinguishes staged content from live content and provides separate publishing workflows. The current connector can complete an item operation while a subsequent site-publishing step fails. A successful item response therefore does not independently prove that the page is publicly updated. See Webflow CMS publishing.Custom webhook
Use a public receiving endpoint, preferably HTTPS. The current URL safety check accepts both HTTP and HTTPS, so do not treat an accepted URL as proof of encrypted delivery. Configure appropriate authentication and validate the receiver’s handling of content and repeated requests. Publishing requests do not follow redirects. Point the integration at the receiving endpoint itself rather than a URL that redirects elsewhere. The manual and scheduled paths differ in accepted success statuses and retry handling; do not assume every response is handled identically. A receiver can accept a request without returning a live URL. A configured URL template can supply a link, but a link alone does not prove that the receiver published the article. In particular, HTTP 202 Accepted means processing has been accepted, not completed; see the HTTP response definition. Check the receiver’s job result and actual website.Where to see what went wrong
Open the blog’s detail page for its current status and publishing error. A scheduled failure can show Publish Failed with Retry Publish available to an authorized editor. A manually triggered request can also report an error without entering that same state. On the destination’s connection card, Last Tested records a previous test and its result; Test Connection runs another check. A past Passed result is useful history, not proof that the current credentials or the next publishing request will succeed. If several posts fail, inspect the shared destination first. If one fails, compare that post’s fields and remote record with a working request. Do not paste private credentials into the article to troubleshoot authentication.How to recover
- Read the current message and record which action failed.
- Inspect the destination for an existing or partially updated post, especially after a timeout.
- Correct the relevant credentials, permissions, content fields, connection, or receiver behavior.
- Run Test Connection where available. Then use the blog’s appropriate action, such as Retry Publish, Publish Now, or Sync Changes.
- Inspect the resulting blog status and actual public page. For a webhook or build receiver, check its downstream result too.
Related
- Connect Platforms: configure the intended destination.
- Publishing Modes & Autopilot: distinguish review-first and automatic workflows.
- Draft & Approval Workflow: review and authorize a draft before publication.
- Webhook Reference: inspect the receiving application’s responsibilities.
