Troubleshooting

Start with the exact affected workspace, channel, post, and approximate time. Keep the request ID shown by the UI or API. Do not share API keys, social tokens, webhook secrets, session cookies, or one-time sign-in codes.

A channel is missing during connection

1. Confirm that you signed in to the intended social account.
2. Check that your native account role can manage and publish to the Page, profile, channel, or location.
3. Verify that the provider supports that account type and region.
4. Re-run the connection and grant the permissions required for the intended capabilities.

If an existing channel has an authentication error, BlendDuck removes it from new publishing while automatic recovery runs. If the provider authorization or native account role changed, use the normal Connect Channel flow again.

See automatic channel recovery for the identity check and failed-target safeguards.

A post cannot be scheduled

• Fix every composer validation warning for every selected target.
• Confirm that the scheduled time is in the future in the displayed timezone.
• Check media type, size, aspect ratio, duration, and provider-specific fields.
• If approvals are required, submit the current version and wait for all stages.
• Confirm that the channel is still connected and supports the chosen post type.

Editing content or changing the approval policy invalidates approval for the older version. Submit the updated version again.

A scheduled target failed

Open the post from Calendar and inspect the failed target, not only the shared post status. Fix the provider error before retrying. Authentication and permission failures usually require reconnecting; validation failures require a content or media change; rate limits should be retried only after the displayed window.

Do not create a duplicate post until you know whether the provider accepted the first request. BlendDuck keeps target state and idempotency information so a safe retry can reuse the same operation.

Inbox or Analytics is empty

• Confirm that the channel exposes the requested capability.
• Check the selected date range, status, channel, and campaign filters.
• Look at the channel's latest sync state and reconnect if authorization failed.
• Remember that provider data can arrive late and that unsupported metrics stay unavailable rather than being estimated.

API returns 401 or 403

• 401 means the bearer credential is missing, invalid, expired, or revoked.
• 403 means the key is valid but lacks the required scope or organization permission.

Send the key only as Authorization: Bearer .... Organization API keys must never be embedded in browser code. Rotate a key that may have been exposed.

API returns 409, 422, or 429

• 409 indicates a state or idempotency conflict. Read the current resource before retrying.
• 422 indicates valid JSON with invalid fields or provider settings. Use the structured error.details entries to locate the field.
• 429 indicates a quota or rate limit. Respect Retry-After and the RateLimit-* headers.

For support, provide the request ID, HTTP method and path, status code, and sanitized input shape. Never include the Authorization header or raw customer content unless the support channel explicitly provides an approved secure path.

Subscription and checkout problems have a separate recovery path in Billing and subscription.