Retry a failed post
Move it back to the queue and investigate the original failure first. Requires post edit access.
Der redaktionelle Inhalt dieses Artikels ist derzeit auf Englisch verfügbar. Die Navigation des Hilfe-Centers ist lokalisiert.
Überblick
Move it back to the queue and investigate the original failure first. Requires post edit access. Use this guide to isolate the cause safely before repeating the action. The calendar and post details show when content is planned, its review and publishing state, and the actions still available.
Identify the symptom
Move it back to the queue and investigate the original failure first. Requires post edit access. 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 Calendar in the organization navigation. Keep the affected item open where possible so you can compare the state after each check.
- Check 1: Move it back to the queue and
Review move it back to the queue and investigate the original failure first and choose the value that matches your intended result.
- Check 2: Requires post edit access
Review requires post edit access 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 post appears on the correct date with the expected state and schedule.
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.
- Clear calendar filters and confirm the visible date range, timezone, page, platform, and post state.
- Open post details to review warnings, approval state, and platform publishing results.
- Refresh after a move, review action, or background publish if the calendar has not updated yet.
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
Die Verfügbarkeit hängt von deinem Organisationszugriff und deinen Berechtigungen ab.