← PostEverywhereCONTENT HISTORY

Update to PostEverywhere

Snapshot Oct 29, 2026 · 19:13 UTC · version 1.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save PostEverywhere and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find and fix social media posts that failed to publish in PostEverywhere. Use when the user says a post didn't go out, a platform failed, an account stopped working, or asks what went wrong with a post.",
  "included_files": [],
  "name": "fix-failed-posts",
  "skill_md_contents": "---\nname: fix-failed-posts\ndescription: Find and fix social media posts that failed to publish in PostEverywhere. Use when the user says a post didn't go out, a platform failed, an account stopped working, or asks what went wrong with a post.\n---\n\n# Fix failed posts\n\nFind what failed, explain why in plain words, fix the cause, and retry only when a retry can work.\n\n## Steps\n\n1. **Find the failures.** Call `list_posts_advanced` with `status: \"failed\"` (and `\"partially_failed\"`), newest first. For one post the user named, call `get_post_results` with its id.\n2. **Read the reason.** Each failed destination carries an error. Sort it into one of these:\n   - **The account needs reconnecting** (expired or revoked login, missing permission). Call `get_account_health` for that account to confirm, then `create_reconnect_link` and give the user the link. They open it and sign in again.\n   - **The post broke a platform rule** (too long, wrong media, missing media). Fix it with `update_post`, then retry.\n   - **A temporary problem** at the platform (rate limit, timeout, the platform was down). Retry.\n   - **Something the user must change on the platform itself** (for example, an Instagram account that isn't a Business or Creator account). Tell them exactly what to change.\n3. **Retry.** For one post, call `retry_failed_post`. For many, call `retry_failed_posts` with the post ids, or filter by `account_id` or `platform`. Don't retry a failure that needs the user to act first; it will fail the same way.\n4. **Confirm.** Call `get_post_results` again after a short wait and tell the user what published.\n\n## Be careful\n\n- Never retry the same post in a loop. One retry after a fix is enough.\n- Retrying a post that already published on some platforms only retries the failed ones.\n"
}

SHA-256 of public snapshot: 81ee2ce267d95d860d1ab56e5cae2afd9d70d3c51bdbe39e27ba0835b9982b60