Errors and retries

Diagnose authentication, validation, media, and async failures without blind retries or duplicate writes.

Read the returned error before changing the request. For REST requests, record the HTTP status and response body. For MCP, inspect the tool result and its isError flag. A request accepted by Blotato still needs its workflow's completion check.

For customer support, use Diagnose and answer to preserve the client, failing stage, previous attempts, and human corrections. Do not repeat a setup question already answered in the conversation.

For missing, delayed, or duplicate posts, follow Find a post's outcome before retrying. An HTTP status or an inaccessible platform URL alone does not establish the underlying cause.

Error or symptom	Next step
401, invalid API key, or invalid session	Follow authentication checks
Subscription-related 403	Check Billing
404	Re-fetch the record and verify the ID type and account
Validation error, often 422	Correct the named field using the endpoint schema
429	Wait for the retry interval if provided, then reduce request frequency
Network error or 5xx on a read	Retry with a delay and a bounded attempt count
Network error after a create request	Check existing work before submitting again
Post status failed	Read errorMessage and the platform requirements
Visual response contains item.error	Stop polling and explain the generation error
Empty analytics or inbox result	Check the feature's sync timing and supported platforms or inbox setup
Media fetch or conversion failure	Follow the media checklist

Inspect a failed request

1. Open the Logs.

2. Select the request.

3. Read its payload, response, and error message.

4. Correct the cause before resubmitting.

For n8n requests, the dashboard's FIX MY AUTOMATION action helps repair the workflow. See the n8n walkthrough. This action is specific to n8n.

Retry without duplicating work

1. Save every submission or creation ID returned by a successful create request.

2. If a status call fails, retry the status call with the saved ID.

3. If creation timed out without an ID, inspect the dashboard and existing posts or schedules before creating another item.

4. For a failed post, correct the error before a new submission. An unchanged retry often fails for the same reason.

5. Set an attempt or elapsed-time limit in your automation. Report unfinished work and its ID when the limit is reached.

Blotato does not expose a documented client-supplied idempotency header for create-post requests. Internal duplicate detection is not a guarantee for arbitrary changed payloads, times, or retries. Retain the submission ID, inspect existing work, and do not invent an idempotency header.

See Error reference, API FAQs, MCP FAQs, and Get support for specific cases.