---
title: "Troubleshoot integration delivery"
description: "Identify the failing stage and choose the relevant recovery action without changing unrelated Project settings."
updated: "2026-09-11"
verifiedAgainst:
  - apps/web/app/app/integrations/page.tsx
  - apps/web/components/publishing-integration-article.tsx
  - apps/web/lib/server/publishing-integrations-service.ts
  - workers/publishing-integrations-delivery.ts
  - workers/publishing-integrations-runtime.ts
  - apps/web/lib/server/publishing-integrations-wordpress-com-oauth.ts
---

Start with the correct active Project and open **Delivery activity**. Connection
verification and article delivery are separate: a **ready** connection establishes
access, while an article becomes **Live** only after its public page is verified.

| Symptom                              | What to check next                                                                                              |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| Integrations are unavailable         | Check Project eligibility, workspace role and the displayed availability message                                |
| A new connection needs attention     | Read its error; check URL, credentials, permissions and provider-specific configuration                         |
| Connecting did not change publishing | Wait for ready, select the full-article destination, then choose Save destinations                              |
| Historical articles did not move     | Existing drafts and bound articles retain their original destination                                            |
| Accepted or awaiting receipt         | The receiver is processing; check its durable work and signed completion receipt                                |
| Retry or attention                   | Fix the reported cause, then use Retry when offered; do not repeatedly create new connections                   |
| Conflict                             | Open the article, inspect the CMS version and complete the available review action                              |
| Summary is hidden                    | Wait for the full version to be verified; ensure the summary supports noindex and renders the full-article link |
| Disconnect is refused                | Finish required withdrawals and pending managed work before removing credentials                                |

## Connection problems

Use [the provider checklist](/integrations/connections). WordPress needs its
companion plugin plus post/media permissions. Ghost needs an **Admin** API key.
Webflow needs the collection fields and a template that renders them. A webhook
or Next.js receiver must support the signed operations, durable identity,
images and withdrawal.

For WordPress.com, start a fresh attempt after expiry or a browser/account
change. Reconnection must select the original site. If provider access was
revoked, reconnect to authorize it again. A failed attempt does not replace the
existing connection. Repeated starts are limited; wait for the attempt window
to expire when the page reports that limit.

## A public article cannot be verified

Check that the returned URL is reachable over public HTTPS and serves the
intended article. A Coming soon page, login screen, broken theme, missing
image, unexpected redirect or CMS-wide noindex setting can change what a reader
or search engine receives. Correct the destination's configuration, then use
the offered delivery retry or article review action.

Managed images are copied to the destination. If an upload fails, check provider
permissions and upload limits. A failed provider reply can leave an unused media
copy; Blogged does not delete possibly shared CMS images automatically.

## Delivery is paused or an article will not withdraw

Check the saved routing state and Project lifecycle. Save the intended
publication destinations to enable delivery again. A request already accepted
by a provider can still finish after a pause. Use **Unpublish** for withdrawal;
wait for all managed copies to confirm it before deleting a bound article.

If the issue persists, contact [support](mailto:hello@blogged.dev) with the Project,
destination, article, time and displayed error. Never include passwords,
application passwords, API keys or signing secrets. Keep generation and billing
settings unchanged while investigating a CMS delivery problem.