Troubleshoot by symptom
Find the next useful check without duplicating posts or losing your original work.
Identify the failing stage
| Symptom | Check first | Next action |
|---|---|---|
| Account missing or disabled | Workspace, selected destination, connection health and role. | Reconnect the intended account if requested; reopen the composer and confirm it is selectable. |
| Draft appears on Calendar but never sends | Actual state and planned date versus scheduled date. | Schedule the reviewed version explicitly; resolve approvals if required. |
| Post is pending approval | Submitting role, reviewer queue and scheduled time. | Have the authorized reviewer inspect it; update a time that passed while waiting. |
| Rejected item cannot be resubmitted | Editable draft versus an older cancelled item. | Edit and resubmit a current draft; duplicate an older cancelled item when needed. |
| Wrong time or apparently missing post | Displayed timezone, date range, account/status filters and queue timezone. | Open post detail and inspect the saved time. Use manual date editing on touch devices. |
| Media rejected | Exact account, placement and validation error. | Export a supported version from the original; verify upload and preview before retrying. |
| Only some accounts succeeded | Per-account result and live destination links. | Fix and retry only failed destinations after checking for an existing live post. |
| Request timed out or stays processing | Returned job/post identifier and current status. | Read the existing operation and destination before creating another request. |
| Queue is idle | Paused state, ready items, future slots, timezone, approval and cooldowns. | Fix the failing condition; inspect Calendar for already materialized scheduled work. |
| Auto-Post finds nothing | Source preview, public feed access and History. | Allow a polling cycle; resolve source errors. Do not reconnect repeatedly to force a backfill. |
| Inbox seems empty | Page load, last-fetch status, filters, supported item type and permissions. | Use the offered fetch control. Confirm the account and send result before replying again. |
| Analytics or report is empty | Selected range/accounts, collection coverage and refresh state. | Broaden the range or wait for data; distinguish unavailable values from zero. |
| AI output or credit estimate surprises you | Current brand context, selected quality and the action estimate. | Refine the brief and review the live estimate before running generation. |
| Integration fails | Authentication, permission, workspace, input validation and rate-limit error. | Use a read-only discovery request and a redacted request identifier for support. |
Preserve evidence before retrying
Record the post/job identifier, failing destination, exact error and time with timezone. Keep original media and drafts. Verify which actions already succeeded so a retry does not duplicate an external post or reply.
Escalate with the smallest useful packet
Send the expected behavior, actual behavior, redacted error, relevant identifier and a screenshot of the affected control. Exclude passwords, keys, signed URLs, unrelated customer conversations and private account records. See Get help and Publishing status and recovery.