Find a post's outcome before retrying

Diagnose missing, delayed, duplicated, or failed posts without assuming an outage or resubmitting an unresolved request.

Use this page when a post disappears from Upcoming Posts, remains in progress, shows published without a visible post, or appears twice. These symptoms do not establish the cause.

Using the Blotato website

1. Record the intended social account or Page, content, and submission or scheduled time with timezone.

2. Check the Scheduled, Published, and Failed filters in Posts for the same destination and content. Check the platform and time-window filters if a record is missing.

3. Open any returned platform URL and check the intended account on the platform.

4. Read the exact error before changing media, reconnecting an account, or retrying.

5. If those records do not establish the result, contact support with the evidence below. Do not submit a replacement while the original outcome is unknown.

Using MCP, REST, n8n, or Make.com

1. Retrieve the postSubmissionId from the original create response. Do not substitute a schedule ID, published-post ID, or guessed UUID.

2. Call blotato_get_post_status or Get Post Status with that ID and the original Blotato account credentials.

3. Follow the status-specific completion rules.

4. Inspect existing posts and schedules when the submission result is missing or inconsistent.

5. Retain the ID when your polling limit is reached. Escalate the unresolved result instead of repeating create-post.

The status endpoint returns in-progress when no matching failed, published, or scheduled record is found. It does not independently confirm a live queue job. A wrong or unavailable submission ID is not proven valid by this status. Verify the original create response before further polling.

Interpret the evidence

Observation	Supported conclusion and next step
Schedule disappeared at its due time	The schedule is no longer in that list. Check publishing results before assuming failure or success.
Published record, but platform URL is absent or inaccessible	Blotato recorded publication. Check the destination and platform account. An inaccessible URL alone does not prove moderation, deletion, or suppression.
Failed result	Read the error and check the destination before retrying. Correct an identified validation or connection problem. Retry a temporary failure only after checking for an existing post.
2 copies on the platform	Record both URLs and submission times. Do not infer a timeout or blame a particular client without request evidence. Ask which copy to keep before removing content through the platform.
Several accounts fail at once	Investigate a shared service or incident. This pattern alone is not proof of an outage or its owner.

Escalation evidence

Include the client, destination, exact error, timestamps with timezone, postSubmissionId when available, relevant request/reference IDs, and platform URLs. State which checks are already complete. Switch to Developer Platform and open Logs for recorded activity. Filter by Posts, Videos, Media, Accounts, or DM, then Processing, Failed, or Success. Search or filter by platform and account. Absence from a filtered log list does not prove no publishing attempt occurred.

Do not share API keys, OAuth codes, or signed upload URLs. Do not promise incident compensation or report a refund, credit adjustment, deletion, or reconnection as completed without confirmation.