> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/social-accounts-and-platform-faqs/facebook/errors.md). # Errors Diagnose Facebook Page publishing errors using the exact response, current account and Page IDs, permission checks, and publication outcomes before retrying. Common Facebook publishing errors and how to fix them. For the full error reference across all platforms, see [Error Reference](/support/errors.md). | Error | Explanation | Fix | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Please reduce the amount of data you're asking for, then retry your request (may also appear as "Could not upload video to Facebook: ...") | The request returned an error. The message does not establish a follower-count threshold, memory exhaustion, or an outage. It also does not prove the post is absent. | Check the Page and original submission through [publication outcome diagnosis](/start-with-an-ai-agent/publishing-status.md). Retain the response and request ID. Retry only after establishing no duplicate would result. Escalate repeated failures instead of changing the destination or media without evidence. | | Could not upload video to Facebook: (#100) The global id xxxxxxx is not allowed for this call | The supplied ID was not accepted for the call. Check its identity and access, not only its spelling. | Retrieve the current [account and Page IDs](/api-and-mcp-concepts/accounts-and-identifiers.md) through the same Blotato credential. Confirm the Page belongs to the selected connection and the required permissions are present. A saved dropdown value is not proof the ID remains valid. | | Error posting to Facebook: (#200) requires pages\_read\_engagement and pages\_manage\_posts permission (the full message may also mention "If posting to a group..." and "requires both pages\_read\_engagement and pages\_manage\_posts as an admin with sufficient administrative permission") | The error names required Page permissions. Blotato publishes to Pages, not Groups or personal profiles. | Confirm the intended Facebook identity has publishing access to the Page. Reconnect that identity and select the intended Page and permissions. If it still fails, retain the Page ID and response for support. Do not remove the integration as a routine next step. See [Facebook connection diagnosis](/settings/social-accounts/facebook.md#a-page-is-missing-or-the-wrong-page-appears). | | Wrong Page ID | Facebook requires both an Account ID and a Page ID. | Copy the Page ID using the "Copy Page ID" button in [Accounts](https://my.blotato.com/accounts). Or use the official Blotato n8n/Make nodes to select the Page from a dropdown. | | Could not upload video to Facebook: There was a problem uploading your video file | This upload failure does not identify a token conflict, invalid media, or another workspace as the cause. | Retain the exact underlying response, request ID, Page ID, and media URL. Check the original post's outcome and [media requirements](/rest-api-reference/publish-post/media.md#facebook). Follow a credential-specific recovery only if the response identifies a credential error. See [account and workspace diagnosis](/social-accounts-and-platform-faqs/facebook/limitations.md#one-blotato-account-per-facebook-account). | | A message asking you to confirm or verify your identity before you can publish (the wording comes directly from Facebook) | The response requests an identity check on Facebook. | Complete the check through Facebook's own app or website while signed in as the Page's authorized user. Do not send identity documents to an assistant. Verify the original post's outcome before retrying from [Posts > Failed](https://my.blotato.com/posts?status=failed) or your automation. | *** **Didn't find your error?** * [Full Error Reference](/support/errors.md) * [API FAQs](/start-with-an-ai-agent/faqs.md) * [General FAQs](/support/faqs.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.blotato.com/social-accounts-and-platform-faqs/facebook/errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.