> 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/support/errors.md). # Error Reference This page contains all Blotato error messages and their explanations. Use your browser's search function (Ctrl+F or Cmd+F) to find your specific error. ## API Errors | Error | Explanation | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Authorization failed - please check your credentials | Double check your Blotato API key. Use the n8n/Make official Blotato nodes for easier setup. You don't have to worry about copy/pasting IDs or raw JSON code. See tutorial: | | Wrong Blotato API Key | Check you've copied the API key correctly without whitespaces. Use the official Blotato n8n/Make nodes for easier setup - you won't need to hardcode API keys manually. See tutorial: | | URL is empty | The URL being passed is empty. Check that previous step finished creating your video/carousel. Increase WAIT time if needed and verify you have enough credits. | | Wrong Account ID | Use the official Blotato n8n/Make nodes - you can select accounts from a dropdown instead of copying IDs manually. See tutorial: . If not using official nodes: Check you've copied the social account ID correctly from Settings > Social Accounts. | | Account \[ID] not found | The accountId in your request does not exist for the user/workspace behind your API key. Use the official Blotato n8n/Make nodes to avoid ID errors -- select accounts from a dropdown instead of copying IDs manually. Install guide: . If you are using MCP or an AI coding tool, your AI tool handles account lookup automatically. Point it to: | | Wrong Page ID | Facebook requires both Account ID and Page ID. Check you've copied Page ID correctly using the "Copy Page ID" button. | | Invalid File Format | Check your file format is valid per social platform requirements. | | Invalid Video Dimensions | Video dimensions not supported by platform. Test with this sample video: | | reached\_active\_user\_cap | Account not properly warmed up. Follow warm-up guide before connecting to Blotato. | | You Ran Out Of AI Credits | Go to Settings > Billing to check and add credits. | | Image or video stuck on "generating" indefinitely | This is not a credits issue. The generation silently failed. Refresh the page and try again. If it persists: create a new video instead of regenerating the stuck one. Check your [API Dashboard](https://my.blotato.com/api-dashboard) for error details. If you have credits but the generation hangs, do not assume credits are the problem. | | 500 Internal Server Error on visual creation | A server-side error occurred. This is not a credits issue. Check your [API Dashboard](https://my.blotato.com/api-dashboard) for the error details. Retry after a few minutes. If using Claude Code or MCP, verify your template ID and inputs are valid. | | Media conversion failed | The media file could not be converted to the format required by the target platform. Common causes: 1) Wrong aspect ratio for Instagram (must be 1:1, 4:5, 1.91:1, or 9:16). 2) Resized templates producing non-standard dimensions. 3) Too many hashtags (Instagram rejects posts exceeding its hashtag limit during media processing). 4) Unsupported codec -- use H.264 MP4 format. Check [Social Platform Requirements](/tips-and-tricks/social-platform-requirements.md) for each platform's specs. | | ClientError: Command failed: ffprobe ... Invalid data found when processing input | The media file itself could not be read -- it is corrupt, incomplete, or not a real video/image file. This often happens when the media URL returned an error page or a truncated download instead of the actual file. This is not a TikTok/Instagram outage and not a credits issue. Re-export or re-download the media, upload a fresh copy (or pass a direct public media URL), then retry from Failed Posts. See: [Troubleshooting Posts that Failed to Publish](/features/content-calendar/tutorial.md#troubleshooting-posts-that-failed-to-publish) | | Could not publish on Instagram: An unexpected error has occurred | This error comes from Instagram/Meta, not Blotato. Troubleshooting steps: 1) Check the [API Dashboard](https://my.blotato.com/api-dashboard) for the full error. 2) Reconnect your Instagram account in [Settings > Social Accounts](https://my.blotato.com/settings). 3) Verify the media URL is publicly accessible (open in incognito). 4) Reduce hashtags and caption length. 5) Increase time between posts. If the error persists after reconnecting, submit a support ticket with the reqId from the error message. | | Unsupported media format (.mov) | Blotato requires H.264 MP4 format for video publishing via API. The .mov format is not supported even if the file is under size limits. Convert your video to H.264 MP4 before uploading or passing via mediaUrls. | | Account \[ID] not found (LinkedIn) | For LinkedIn company pages, you need both an accountId and a pageId. A common mistake is passing the pageId where accountId is expected. Use `GET /v2/users/me/accounts` to get the accountId, then `GET /v2/users/me/accounts/{accountId}/subaccounts` to get the pageId. Pass accountId in `post.accountId` and pageId in `post.target.pageId`. See: [Accounts API](/api/accounts.md) | | 503 Service Unavailable | The social platform or a connected service is temporarily down. This is usually a platform-side outage, not a Blotato issue. Wait a few minutes and retry. If the error persists, check the platform's status page. | | 504 Gateway Timeout | The request took too long and timed out. This happens when the social platform does not respond within the allowed time. Retry after a few minutes. If it keeps happening, reconnect the account in [Settings > Social Accounts](https://my.blotato.com/settings). | | Wrong Template Parameters | Each video template has different parameters. Check API docs for correct template parameters. | | Missing AI Voice | POV template doesn't include AI voice. Use empty template ID for AI voiceover. | | Missing Music | Add autoAddMusic: true parameter in PUBLISH TO TIKTOK step for music. | | Wrong Heygen API Key and IDs | Check you've copied HEYGEN AVATAR ID correctly, not the Avatar GROUP ID. | | You're On Heygen Free Plan | HeyGen API requires $99/mo API plan. Free API plan won't work. | | Your Avatar Has a Background | Set matting to false and remove background section for default avatar background. | | Invalid JSON Error | Validate JSON at jsonlint.com and compare with Blotato API docs. | | The service is receiving too many requests from you | Rate limit exceeded. Upload Media: 30 requests/minute. Publish Post: 30 requests/minute. | | Exceeded rate limits (repeated YouTube or LinkedIn publish failures) | The platform is rate-limiting publishing for your connected account. Wait an hour and retry from [Failed Posts](https://my.blotato.com/failed). If posts keep failing with this error after waiting, reconnect the social account in [Settings > Social Accounts](https://my.blotato.com/settings), then retry the post -- a stale connection token keeps triggering the platform's rate limiter. | | Unsupported media format: mov,mp4,m4a,3gp,3g2,mj2 (X/Twitter or LinkedIn post failed) | Misleading error text -- your file format is usually fine. The real failure is most often video duration: X (Twitter) requires between 0.5 and 140 seconds, and if Blotato has to convert the video it must be under 120 seconds. Check the video length first and trim if needed. If length is fine, pre-encode to the platform's exact spec (H.264/AAC MP4) so no conversion runs. See [Social Platform Requirements](/tips-and-tricks/social-platform-requirements.md) and [X FAQs](/platforms/faqs.md). | | The aspect ratio is not supported | Video aspect ratio not supported by platform. Check platform requirements. | | body/template/id must be equal to constant | Pass template object with id. See API examples for correct format. | | scenes.0: missing object | Incorrect JSON format for scenes array in CREATE VISUAL node. Each template has a specific scenes format -- find your template's exact format with examples at [Visual Templates](https://help.blotato.com/api/visuals). To debug: (1) Select template in n8n/Make, (2) Remove ALL parameters including Prompt, (3) Run the step, (4) Check [API Dashboard](https://my.blotato.com/api-dashboard) to see the exact JSON structure your template expects. | | slides.image: must be at most 400 characters | The image field expects a short public URL (e.g. ), not a base64 string or data blob. Keep image URLs under 400 characters. | | mediaURL is null or empty | Video not done. Increase wait time or check if you have AI credits. | | Cannot read properties of undefined (reading 'mediaUrl') | You're trying to publish before the visual/video is finished rendering. After your Create Visual step, add a Get Visual step and wait until the status is "done", then map the mediaUrl into the Publish step's Media URLs field. If the visual creation failed or you ran out of AI credits, the mediaUrl will never be produced. | | Cannot read properties of undefined (reading 'status') | The social platform (Instagram, TikTok, etc.) did not return a response. This is usually a temporary issue. Wait a few minutes and retry. If the error persists, check that your media file is in a supported format: [Social Platform Requirements](/tips-and-tricks/social-platform-requirements.md). In the web app, retry from the [Failed Posts](https://my.blotato.com/failed) screen. | | Failed to upload stream to Supabase | The media file could not be saved to storage. Common causes: the source URL is not publicly accessible, the URL points to a preview page instead of the direct file, the file is too large, or the media file is corrupted. Open the media URL in an incognito browser window to verify it downloads directly. If using Google Drive, use a direct download link, not a /view link. | | Failed to fetch media URL: char '...' is not expected.:1:1 (often shown in n8n alongside "Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.") | Blotato downloaded the URL in your `mediaUrls`, but the response was not binary media -- it was plain text (the first character of that text shows up in the error, e.g. `e` for "expired" or "error..."). Open `{error}.$response` in n8n to read the actual body the URL returned. Common causes: 1) Signed URL expired before Blotato fetched it (Canva exports, S3 presigned URLs, Google Drive). 2) URL points to a preview page or folder, not a direct file (e.g. Google Drive `/view`). 3) Auth or CDN bot protection on the host. Fixes: For Google Drive use `https://drive.usercontent.google.com/download?id=FILE_ID&export=download&confirm=t`. For Canva, pass the export URL directly into `mediaUrls`. For local files, upload via Blotato's presigned upload flow and publish using the returned `publicUrl`. If you uploaded the video directly from your computer (no external URL) and the post keeps failing with this error, the stored file reference is bad -- retrying alone does not fix it. Re-upload instead: 1) move the failed post back to Drafts, 2) remove the current video and upload the MP4 again so it gets a clean file reference, 3) reschedule the post. Also confirm the file is a standard MP4, not corrupted, and within your plan's upload size limit ([Plan Limits](/settings/billing-and-credits.md#plan-limits)). See: [Posts failing with "Could not fetch media"](/api/mcp/examples.md#posts-failing-with-could-not-fetch-media). | | Please review our URL ownership verification rules | TikTok rejects certain URLs. Try using a different hosting service for your media, or use the optional Blotato Upload endpoint first: | | Tiktok's servers may be experiencing issues. This is a retryable error | TikTok server issue or posting too frequently. Wait and retry. | | Could not refresh TikTok access\_token: Service Unavailable | TikTok's servers temporarily rejected the token refresh. Wait 15-30 minutes and retry. If the error persists, reconnect your TikTok account in [Settings > Social Accounts](https://my.blotato.com/settings). | | JSON value expected but got '<' at position 0 (TikTok) | TikTok's API returned an HTML error page instead of a JSON response. This is a temporary TikTok server issue (outage, rate limiting, or maintenance). Your post payload is valid. Retry after a few minutes. If it keeps failing, reconnect your TikTok account in [Settings > Social Accounts](https://my.blotato.com/settings). | | Threads API Feature Not Available: This user does not have access to this Threads API feature | Link Instagram account to Threads. Warm up Threads account for a few days with posts before connecting to Blotato. | | Failed to read media metadata. Is the file accessible and a valid media file? | Three causes, in order of likelihood: 1) **File not publicly accessible.** Open the URL in an incognito browser and confirm it downloads the raw file. For Google Drive, set the file to "Anyone with the link" as Viewer and use a direct download URL: `https://drive.usercontent.google.com/download?id=FILE_ID&export=download&confirm=t` 2) **The file host throttles or interferes with server-side fetches.** Hosting behind GoDaddy, Cloudflare, or similar CDN/bot protection can slow or garble Blotato's server-to-server download enough that metadata reading fails, especially on larger files (tens of MB) -- even when `curl` from your machine returns HTTP 200 with `content-type: video/mp4`. Fix: move the file to a host without bot protection (a public S3/GCS bucket or similar), or switch to the [Presigned Upload](/api/publish-post/upload-media-v2-media.md#presigned-upload-local-files) flow, which handles large binaries via direct PUT and skips the URL fetch entirely. Also confirm the file is within your plan's upload size cap: 400MB on Starter, 1GB on Creator and Agency ([Plan Limits](/settings/billing-and-credits.md#plan-limits)). 3) **Intermittent metadata-reader flake.** If the exact same call on the same small file passes sometimes and fails other times, the URL is not the problem. Wrap `/v2/media` in a 2-attempt retry with a 3-second delay, or switch to presigned upload, which runs through a different code path and avoids the issue entirely. | | Google Drive virus scan warning popup blocking media access | Google Drive shows virus scan warnings for large files (>25MB typically) or files it cannot scan. This blocks automated access to your media. **Solutions**: 1) Use the direct download URL format: `https://drive.usercontent.google.com/download?id=FILE_ID&export=download&confirm=t` which bypasses the warning page. 2) For files >50MB, use a different hosting service like AWS S3, Dropbox, or direct server hosting instead of Google Drive. 3) For automation workflows, consider using cloud storage with proper API access rather than Google Drive shared links. | | Base64 data is too large, maximum size is 20MB | This error happens when uploading media larger than 15MB via the n8n Upload "Binary Data" option. Switch to URL-based upload: use the [Presigned Upload](/api/publish-post/upload-media-v2-media.md#presigned-upload-local-files) endpoint to upload directly to Blotato, or host on AWS S3/GCP and pass the URL. See: [Plan Limits](/settings/billing-and-credits.md#plan-limits) for more details on max upload sizes. | | Visual creation fails or images are blank when using self-hosted image URLs | Your server's firewall or CDN (e.g., Cloudflare) is blocking Blotato from fetching your images. Blotato's servers make server-to-server requests to download media, which bot-protection rules block. Add a firewall rule to allow these requests, or host your images on a service without bot protection (e.g., a public S3 bucket, Imgur, or the Blotato [Upload endpoint](https://help.blotato.com/api/api-reference/upload-media-v2-media)). Test accessibility with `curl ` from another server. | | Error posting to Instagram: No error |

I've noticed a recent glitch with Instagram API that sometimes returns "No Error" and video rejected, but this looks like an issue on IG side, as I haven't changed anything on the Blotato side. I'll keep monitoring it, but I generally recommend the following:

  • reduce the number of hashtags
  • reducing the length of caption
  • increasing time between posts
| | Could not publish on Instagram: Error validating access token: Sessions for the user are not allowed because the user is not a confirmed user | This error comes from Instagram/Meta. The Instagram account session is not confirmed. To fix: 1) Log into the Instagram account in a browser and complete any pending prompts (email/phone confirmation, security checkpoints, updated terms). 2) Reconnect the account in Blotato: go to Settings > Social Accounts, disconnect and reconnect using an incognito browser logged into only that Instagram account. 3) Verify the account is a Professional or Business account (personal accounts have issues with third-party publishing). See: | | Instagram allows a maximum of 5 hashtags per post | This is a Blotato guardrail, not an Instagram rule. Instagram itself allows more hashtags, but Blotato caps posts at 5 on purpose because more than 5 hashtags reduces your reach on Instagram, TikTok, and Facebook. Fix: trim your caption to 5 hashtags or fewer and republish. See [hashtag rules by platform](/tips-and-tricks/social-platform-requirements.md#hashtags) and [how many hashtags to use](/support/faqs.md#how-many-hashtags-should-i-use). | ## Source / Ingestion Errors | Error | Explanation | | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | TikTok video has no captions / transcript extraction failed | Blotato extracts the transcript from TikTok videos to use as a source. If the TikTok video has no captions (subtitles), Blotato cannot pull the transcript. Try a different TikTok video that has captions, or copy-paste the video's content as a Text source instead. | ## Connection Errors | Error | Explanation | | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 400 Session Error Connecting Instagram Account | Sometimes connection succeeds despite error. Test with a post first. If not, use incognito browser, log out of other accounts, log into only the target account, then reconnect. | | Unable to connect LinkedIn company page | Verify you're an Admin of the page. Use incognito browser, log into social account, then Blotato, and reconnect. | | YouTube Unauthorized error | Use incognito browser. Log into YouTube, then Blotato. Reconnect account. Update YouTube account ID in automation workflows. | | Unable to connect social account (general) | Use incognito Chrome browser. Log into social account first, then Blotato. Connect account. | | invalid\_grant (Instagram/Meta) | The Instagram/Meta authorization token expired. Go to [Settings > Social Accounts](https://my.blotato.com/settings), find the Instagram account, and click Reconnect. This error often causes follow-on "mediaUrl" TypeErrors -- fix the token first. | | invalid\_grant (Claude Cowork / MCP) | Your Blotato MCP OAuth connection expired. In Claude, open **Customize > Connectors**, remove and re-add the Blotato custom connector, and re-approve access via OAuth. This is separate from reconnecting a social account. See: [MCP Setup](/api/mcp/setup.md) | | Blotato shows "Connected" in Claude Settings, but Claude.ai returns an OAuth error when asked to list accounts | Blotato API and MCP require a paid subscription. Go to [Settings > API](https://my.blotato.com/settings/api) and click "Generate API Key" to activate your paid subscription. | ## Comments Errors | Error | Explanation | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Comment failed to post (error code 20201) | The social platform rejected the comment. Check the comment's `errorMessage` for the reason. Common causes: the parent post was removed, the comment triggered the platform's spam rules, or the account lost comment permissions. Reduce how often you comment and retry. See [Comments API](/api/comments.md). | | Active contacts limit reached (error code 20101) | You reached the maximum active contacts for your plan this month by replying to audience comments (Starter 100, Creator 250, Agency 1000). Your count resets at the start of next month. Upgrade your plan to raise the limit. See [Comments API](/api/comments.md). | ## Messaging Errors | Error | Explanation | | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Active contacts limit reached (error code 20101) | You reached the maximum active contacts for your plan this month by messaging new people. Your count resets at the start of next month. Upgrade your plan to raise the limit. See [Active Contacts](/settings/billing-and-credits.md#active-contacts). | | Message failed to send (error code 20102) | The social platform rejected the message. Check the message's `errorMessage` for the reason. Common causes: the 24-hour messaging window closed, the comment you replied to is invalid, or the account lost messaging permissions. See [Messages API](/api/messages.md). | ## Platform-Specific Errors | Error | Explanation | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Post failed to publish. Could not upload video | Each platform has different requirements for video uploads. Check that your video follows the requirements here: | | Video duration exceeds the maximum convertible duration of N seconds | Your video required conversion (resizing, re-encoding, bitrate adjustment, etc.) to meet the platform's format requirements, but the video is too long to convert. Blotato caps video conversion at 2 minutes, even when the target platform allows longer videos. To fix: 1) Trim your video to under 2 minutes; or 2) Pre-encode your video to match the platform's specs exactly (correct codec, aspect ratio, resolution, bitrate) so no conversion is needed. Check [Social Platform Requirements](/tips-and-tricks/social-platform-requirements.md) for each platform's specs. | | The user has exceeded the number of videos they may upload (YouTube) | YouTube upload limit reached. Wait 24 hours. Check API quota in Google Cloud Console. Verify account. | | You have reached the maximum number of 10 posts for the last 24 hours for this account (YouTube) | YouTube enforces a limit of 10 uploads per channel per 24 hours via API. Wait 24 hours and try again, or upload directly via the YouTube website. This is a YouTube limit, not a Blotato limit. | | You have reached the maximum number of 25 posts for the last 24 hours for this account (Facebook) | Facebook publishing is limited to 25 posts per 24 hours per Page. Each Page has its own independent limit. Wait 24 hours and try again, or publish to a different Page. | | You have reached the maximum number of 50 posts for the last 24 hours for this account (LinkedIn) | LinkedIn publishing is limited to 50 posts per 24 hours per profile and per company Page. Each profile and company Page has its own independent limit. Wait 24 hours and try again, or publish to a different profile or company Page. | | Unsupported picture size (TikTok) | TikTok rejects images that do not meet its format requirements. TikTok accepts WebP and JPEG only (no PNG). Max resolution: 1080 pixels. Max file size: 20 MB per image. Convert PNG images to JPEG before posting. Full specs: [Social Platform Requirements](https://help.blotato.com/tips-and-tricks/social-platform-requirements#tiktok) | | TikTok views consistently < 50 | Account likely shadowbanned. Start fresh with new account. | | TikTok views consistently \~200 | TikTok doesn't know your video topic. Use niche keywords in title, description, and audio. | | Single TikTok video stuck at low views | Change video privacy to PRIVATE, close app, reopen, switch back to EVERYONE. | | TikTok account banned | Account not warmed up properly. Follow warm-up guide. Don't post more than 3x/day via API. Stay active on account. | | Escape Multi-Line Paragraphs error | Long text with linebreaks needs escaping. In n8n use toJsonString() function. | | Brand New Account error | Account not warmed up. Don't connect 3rd party apps until account is established with manual posts. | | Sorry! This site doesn't allow you to save Pins. | This error is from Pinterest. Two common causes: 1) The website indicated they do not want to be pinned. 2) Pinterest's blocklist flagged your URL (often a false positive). Workaround: append parameters to your link (e.g., `?ref=pin&v=111`) so Pinterest sees it as a new URL that bypasses the filter. | | Pinterest API access is temporarily restricted to verified accounts only | Your Pinterest still looks pretty new. You MUST warm it up for 2 weeks before connecting to 3rd party posting tools like Blotato. Failing to do this often results in being shadowbanned or flagged by Pinterest. Start posting 1 pin per day manually, then gradually ramp up to 2, then 3, etc. pins per day. Once you get 100+ views per month, then reconnect your Pinterest account with Blotato and it will be automatically verified. | | 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") | Facebook Page permissions are incomplete or partially authorized, or you do not have a full Admin role on the Page. Blotato publishes to Facebook **Pages** only -- it cannot post to Facebook **Groups** or personal profiles. Go to [Settings > Social Accounts](https://my.blotato.com/settings), click Reconnect for your Facebook account. In the Meta permissions popup, select "Opt in to current Pages only" and check each Page individually. Confirm you have a full **Admin** role on the Page (an Editor, Advertiser, or Analyst role is not enough) -- [check your Page role](https://www.facebook.com/help/510247025775149). If the Page still fails, remove the Blotato app from Meta Business Suite (Settings > Accounts > Apps) and reconnect fresh. See: [Facebook Connection Guide](/settings/social-accounts/facebook.md) | | Please reduce the amount of data you're asking for, then retry your request (may also appear as "Could not upload video to Facebook: ...") | Facebook/Meta API server-side error -- not a Blotato bug. It is more common on larger Pages or groups, often around 5,000+ followers, because Facebook may run out of memory while processing the publish request, and it can affect any post type (text, image, link, or video). Retry publishing the post -- it often succeeds on a later attempt. First check the Facebook Page, because the post can sometimes publish successfully even though the API reports a failure. If it did not publish, wait a few minutes and retry from [Failed Posts](https://my.blotato.com/failed). If the post uses Page mentions, try removing the mention and adding it manually later on Facebook. If the error persists across multiple retries over an hour, submit a support ticket via in-app chat with the post ID, timestamp, and Facebook Page follower count. See: [Facebook Errors](/platforms/facebook/errors.md) | | Error posting to Instagram: We restrict certain activity to protect our community. | Instagram made a final decision based on risk/spam scores. To fix: 1) Reduce the number of hashtags. 2) Reduce your caption length. 3) Increase time between posts. 4) If none of the above works, try posting manually to warm up your account and prove to Instagram you're not a bot. | | Cannot read properties of undefined (reading 'mediaUrl') | This Instagram-specific error has multiple causes: 1) Expired Instagram token -- check for `invalid_grant` errors in your [API Dashboard](https://my.blotato.com/api-dashboard) and reconnect the account in [Settings](https://my.blotato.com/settings). 2) The `content.mediaUrls` array is empty or contains URLs that are not publicly accessible. 3) In n8n/Make workflows, the node upstream of the Publish node is not outputting a media URL -- verify the Create Visual step completed with status "done". Fix the token first, as expired tokens cause this error most frequently. | | Could not publish on Instagram: Unsupported post type. The post has too little or too many attachments to qualify as a carousel | Via API, Instagram supports a maximum of 10 images or videos per carousel. See: | | This user is not allowed to post a video longer than 2 minutes (X/Twitter 403 Forbidden) | Two causes: 1) Free X accounts are limited by X to 2-minute videos -- posting longer videos requires X Premium. 2) X Premium accounts also hit this error when Blotato has to convert the video, because Blotato caps video conversion at 2 minutes regardless of your X plan. Fix for X Premium accounts: pre-encode your video to match X's specs exactly (H.264 video codec, AAC audio codec, MP4 container) so Blotato skips the conversion step and uploads the file as-is -- then X Premium's longer video limit applies. Full specs: [Social Platform Requirements](/tips-and-tricks/social-platform-requirements.md#twitter) | | You are not permitted to perform this action (X/Twitter 403 Forbidden) | Twitter/X authorization expired or permissions changed. Go to [Settings > Social Accounts](https://my.blotato.com/settings), find your Twitter account, and click Reconnect. Re-authorize the app when prompted. Retry your post after reconnecting. | | You are not allowed to create a Tweet with duplicate content (X/Twitter 403 Forbidden) | X/Twitter rejects posts with identical text to a previous tweet on your account. Change the caption text (even slightly) before reposting. If you scheduled the same post twice by accident, delete the duplicate from [Upcoming Posts](https://my.blotato.com/queue/calendar). | | Post published twice / duplicate post | A timeout during publishing caused Blotato to retry, resulting in two posts on the social platform. Delete the duplicate from the social platform. If this happens repeatedly, submit a support ticket with the post URLs and timestamps. | | Bluesky posts publish without images (API) | Known bug affecting image attachments to Bluesky posts via API. The post publishes but images are missing. Contact support via in-app chat for status updates. | | Unsupported picture size (TikTok) | TikTok rejected the image. Ensure the image is in JPEG or WebP format (not PNG), under 20 MB, and max 1080 pixels resolution. See: [Social Platform Requirements](/tips-and-tricks/social-platform-requirements.md#tiktok) | | The parent job ... cannot be replaced. addJob | This error comes from the internal media conversion queue when multiple publish attempts try to use the same job ID instead of creating a new one. Common causes: 1) Your automation runs parallel publish attempts for the same post, 2) WAIT time too short - previous conversion still in progress, 3) Publishing before mediaURL/asset is ready. Fix: In n8n/Make automations, ensure only one publish attempt runs at a time and wait for mediaURL to be ready before publishing. Check API Dashboard for the exact failed request details. | | Failed to publish TikTok post after 3 retries (Unknown error reason) | Temporary TikTok-side outage, not a Blotato issue and not a credits issue. Retrying immediately or reconnecting the account usually will not help, and a public status page will not always show it (some outages affect only certain regions or posts from external URLs). Wait a few hours and retry from [Failed Posts](https://my.blotato.com/failed). If several recent TikTok posts fail at once, message in-app chat support to confirm a known TikTok outage and receive +3000 credits for the inconvenience. | | TikTok post disappears and never appears (stuck "buffering," not in Failed Posts) | The post leaves Upcoming Posts, then never shows on TikTok, in Published Posts, or in Failed Posts, with no request in the [API Dashboard](https://my.blotato.com/api-dashboard). This is a TikTok-side issue processing videos from external URLs -- the post stays stuck in "publishing" so TikTok never returns success or failure, which is why it does not land in Failed Posts. Not a credits or Blotato queue issue, and can affect only certain regions (for example, European accounts). Wait a few hours, then repost with a longer lead time. Message in-app chat support with the account name and scheduled time to confirm a known TikTok outage and receive credits. See: [TikTok FAQs](/platforms/tiktok/faqs.md). | | Post shows "published" but does not appear on the platform | The social platform accepted the post but later delayed or suppressed it. Wait 10-15 minutes, then check the post URL from [Published Posts](https://my.blotato.com/queue/calendar). If the URL returns 404, the platform removed it (spam filter, account health). Reduce posting frequency and engage organically. | | Could not schedule post: No available slot time found in the next 9 months (also shown as "in the next year") | No schedule slots exist for the platform/account you are scheduling to. This appears in the web app when you pick "Next Free Slot", and via API when you set `useNextFreeSlot: true`. Slots live on the [Schedule Slots](https://my.blotato.com/queue/slots) page, not the Calendar page. In the web app: open [Schedule Slots](https://my.blotato.com/queue/slots), click "+ Add Slot", pick a day and time, and assign the slot to the exact platform/account you are posting to. Each slot is platform-specific -- a slot for "Instagram" does not match a LinkedIn post, so create slots for every platform you schedule to. See: [Schedule Slots API](/api/schedule-slots.md) | | Post shows CANCELED | CANCELED is a post status, not a publishing error. A post is marked canceled when its schedule was removed before it published: the scheduled post was deleted, moved back to drafts in the calendar, or removed via `DELETE /v2/schedules/:id` through the API. Nothing failed on the social platform, and it is different from FAILED (a permanent publishing error). If you meant the post to go out, open it and schedule it again. | ## Plan Limit Errors These errors are returned when you exceed one of your Blotato plan limits. For the full table of limits per plan, see [Plan Limits](/settings/billing-and-credits.md#plan-limits). | Error | Explanation | | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | You have reached the maximum number of connected accounts (N) for your plan. Please disconnect some accounts or upgrade your plan. | You hit the connected-accounts cap for your plan. Disconnect an account in [Settings > Social Accounts](https://my.blotato.com/settings) or upgrade. Each connected Facebook Page counts toward the limit (the Facebook login does not), and for LinkedIn your profile plus each connected company Page count. See: [Plan Limits](/settings/billing-and-credits.md#plan-limits) | | You have reached the maximum number of scheduled posts (N) for your plan. Please remove some scheduled posts or upgrade your plan. | You hit the queued-scheduled-posts cap. Delete upcoming posts from [Upcoming Posts](https://my.blotato.com/queue/calendar) or upgrade your plan. See: [Plan Limits](/settings/billing-and-credits.md#plan-limits) | | Scheduled time is too far in the future. | Your scheduled time is past your plan's horizon. Pick a time within your plan's window or upgrade. See: [Plan Limits](/settings/billing-and-credits.md#plan-limits) | | File exceeds the maximum upload size (N MB) for your plan. Upload a smaller file, or upgrade your plan to increase your max upload size. | Your media file is larger than your plan's upload cap. Compress or trim the file, or upgrade. See: [Plan Limits](/settings/billing-and-credits.md#plan-limits) | ## Account Limits | Platform | Limit | Explanation | | --------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | TikTok (Starter Plan) | 3 unique accounts per 24h, 10 posts per account | Limit applies to Starter plan only. Creator and Agency plans unrestricted. | | Instagram | 50 posts per day per account | Hard limit per 24-hour window. | | LinkedIn | 50 posts per 24h per profile and per Page | Your profile and each connected company Page each have their own independent 50-post limit. | | Pinterest | 10 pins per day per account | Auto-verified by Blotato when you reconnect, provided your Pinterest has 100+ monthly views from a 2-week manual warm-up (1 pin/day ramping to 3/day). | | Facebook | 25 posts per 24h per Page; 5 per day per Page recommended | Each Page has its own independent 25-post limit, so posts to one Page do not count against another. Posting above 5 per day per Page also negatively impacts post reach. | | YouTube | 10 uploads per channel per 24h via API | YouTube-enforced limit. New channels may have lower quotas. Upload via YouTube website to bypass. | For full details on platform posting limits, see: ## App Errors | Error | Explanation | | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Application error: a client-side exception has occurred while loading my.blotato.com | This is almost always a browser issue, not your account. Start with a hard refresh. If it persists, follow the full checklist in [App Won't Load (client-side exception)](#app-wont-load-client-side-exception) below. | ## Troubleshooting Steps ### App Won't Load (client-side exception) If you see "Application error: a client-side exception has occurred while loading my.blotato.com" (often after a few loading screens, and you cannot log in), it comes from your browser, not your Blotato account. Work through these steps in order: 1. Refresh the page first. This clears it more often than you would expect. 2. Open [my.blotato.com/login](https://my.blotato.com/login) in an incognito window, logged out of other accounts. 3. Still stuck? Try a different browser or your phone to see if the issue is only on one device. 4. Turn off ad blockers and privacy extensions (uBlock, Ghostery, and similar), then reload. 5. Clear site data for blotato.com only: click the padlock by the URL, open Site settings, click Clear data, then log in fresh. 6. If none of that helps, open the browser console when the error shows (right-click the page, Inspect, Console tab), screenshot it, and send it to support through the in-app messenger. ### General Connection Issues 1. Open incognito Chrome browser 2. Log out of all other accounts 3. Log into target social account only 4. Log into Blotato 5. Connect account ### API Issues 1. Check your [API Dashboard](https://my.blotato.com/api-dashboard) - click on any request to see the full payload, error response, and which account it was sent to 2. Verify API keys copied correctly without spaces 3. Check you have sufficient AI credits 4. Validate JSON at jsonlint.com 5. Compare your request with API documentation ### Account Health Issues 1. Warm up new accounts manually for several days 2. Post organically before connecting to Blotato 3. Stay active on account (reply to comments, engage) 4. Don't exceed platform posting limits 5. Use platform-appropriate content formats --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.blotato.com/support/errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.