Understand page status: OK, warning, and error

Überblick

Token expiry, missing scopes, spam warnings, and the “collecting data” state. Core. Use this guide to isolate the cause safely before repeating the action. Connected pages supply the publishing, comment, reporting, and audience data used throughout MediaFox.

Identify the symptom

Token expiry, missing scopes, spam warnings, and the “collecting data” state. 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 Page Management in the organization navigation. Keep the affected item open where possible so you can compare the state after each check.

1. 1
   Check 1: Token expiry

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

2. 2
   Check 2: Missing scopes

   Review missing scopes and choose the value that matches your intended result.

3. 3
   Check 3: Spam warnings

   Review spam warnings and choose the value that matches your intended result.

4. 4
   Check 4: The “collecting data” state

   Review the “collecting data” state and choose the value that matches your intended result.

5. 5
   Check 5: Core

   Review core 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 page card shows the correct connection state, permissions, and latest available data.

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.

• Confirm that the social account grants the requested platform permissions and that you selected the correct page or channel.
• Reconnect an expired connection from Page Management and complete every authorization screen.
• If the page is hidden, clear active filters and ask an owner to verify page access for your role.

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.

Verfügbarkeit und Zugriff

Ähnliche Anleitungen