Troubleshoot scheduled or failed posts

Overview

Platform validation, page token, scheduling/timezone, platform/API restriction, log timeline, Retry posting, and when to reconnect a page. Core. Use this guide to isolate the cause safely before repeating the action. Security and troubleshooting depend on precise timestamps, states, permissions, service health, and reproducible steps.

Identify the symptom

Platform validation, page token, scheduling/timezone, platform/API restriction, log timeline, Retry posting, and when to reconnect a page. Core. Note the exact point where the actual behavior differs from what you expected.

Do not repeatedly submit, delete, publish, reconnect, or purchase while the result is uncertain. First verify whether the previous action completed in another tab, activity list, Audit Log, or external platform.

Checks to make in order

Start in Audit Log, System Status, or the affected feature. Keep the affected item open where possible so you can compare the state after each check.

1. 1
   Check 1: Platform validation

   Review platform validation and choose the value that matches your intended result.

2. 2
   Check 2: Page token

   Review page token and choose the value that matches your intended result.

3. 3
   Check 3: Scheduling/timezone

   Review scheduling/timezone and choose the value that matches your intended result.

4. 4
   Check 4: Platform/API restriction

   Review platform/API restriction and choose the value that matches your intended result.

5. 5
   Check 5: Log timeline

   Review log timeline and choose the value that matches your intended result.

6. 6
   Check 6: Retry posting

   Retry posting.

7. 7
   Check 7: When to reconnect a page

   Review when to reconnect a page and choose the value that matches your intended result.

Safe recovery

After correcting the cause, refresh the page and repeat the smallest safe action that can prove the workflow works. The issue is resolved when the cause is identified, the safe recovery action is complete, or support has enough context to investigate.

If a retry could publish, delete, charge, revoke access, retire a public address, or send a message twice, contact an owner or support instead of guessing.

• Record the organization, route, item ID, time and timezone, exact message, and steps that reproduce the issue.
• Check System Status and Audit Log before repeating a destructive or security-sensitive action.
• Never send passwords, verification codes, cookies, access tokens, API keys, or other secrets.

If you still need help

Send support the organization name, route, affected item ID, timestamp and timezone, exact message, screenshot, and reproducible steps. Include the relevant System Status or Audit Log entry when available.

Never send passwords, verification codes, cookies, access tokens, API keys, payment details, or other secrets.

Availability and access

Related guides