Fix Instagram account unavailable errors

You open the dashboard at 8:55 a.m. to check the Reel you queued last night. The status reads "account unavailable" and the post never reaches Instagram.

Verify credentials first

Open Platform Settings and confirm the Instagram token has not expired. Tokens issued through the Meta Business API last 60 days before they require renewal. Paste the new token, save, and run a test publish to a private test account.

Reconnect the account if the token field shows an error code 190. FlixySocial stores tokens encrypted at rest, so a fresh login from the same browser session usually clears the flag.

Check token scopes

The required scopes are instagram_basic, instagram_content_publish, and pages_read_engagement. Missing any one of these three blocks every scheduled post.

Review recent activity limits

Instagram enforces unpublished post limits that reset every 24 hours. If you sent 25 posts in the last day, the next attempt returns the unavailable message until the window rolls over.

Look at the activity log inside Dashboard. Filter by Instagram and count rows with status 429. If the count exceeds 20, space future posts at least 45 minutes apart for the next 48 hours.

Update posting workflow in Compose

Switch to Compose and select the Instagram destination before writing the caption. The form automatically strips unsupported characters such as the emoji sequence U+1F1FA U+1F1F8 that sometimes triggers moderation flags.

Set the publish time to at least 15 minutes after the current clock time. Immediate posts bypass the queue and hit rate limits faster than delayed ones.

Handle two-factor prompts

When Instagram sends a 2FA code to the linked phone, approve it inside the FlixySocial mobile app within 90 seconds. Codes older than two minutes cause the account to appear unavailable for the next six hours.

Log the approval timestamp in a simple text file so the team knows the exact window before the next scheduled item.

Confirm account status outside the tool

Log into instagram.com from an incognito window. If the profile loads but the business dashboard shows a restriction notice, wait 72 hours before attempting another publish. During that period route content to Threads or X instead.

Compare publish formats

Format	Max duration	Caption limit	Common unavailable trigger
Reel	90 s	2200 chars	Audio track flagged for copyright
Photo	n/a	2200 chars	Aspect ratio outside 4:5 to 1.91:1
Carousel	10 images	2200 chars	One image exceeds 8 MB

Use the table to match your file specs against known triggers before the next batch.

After you restore the connection, the same Reel from the opening scenario published at 9:17 a.m. with no further errors. Repeat the credential check inside Platform Settings each month to keep the queue moving.

Batch caption export

Export the caption file as UTF-8 .txt before import. FlixySocial reads the first line as the primary text and any subsequent lines as alt text for accessibility.

Storage path example

Save assets in /projects/client-0426/reels/2026-07-08-take3.mp4. The date folder keeps the Dashboard search fast when you later review performance metrics.

Approval handoff

Assign the draft to a reviewer from the team list. The reviewer receives an email with a direct link to the post in Compose. Once approved, the status changes to scheduled and the unavailable flag clears on the next sync.

Analytics review cycle

Every Monday pull the prior week's Instagram reach numbers. Compare reach before and after the unavailable incident. A drop of more than 15 percent usually means the token needs rotation again.

Privacy note

All tokens remain on your server. Delete them at any time from Data Deletion if you move the account to another publishing system.

Audit media file specifications

Before scheduling any Reel or carousel, run a local file check using the same dimensions and bitrate Instagram accepts. Open the asset in a media inspector and confirm the video codec is H.264 with AAC audio at 48 kHz. Files encoded with HEVC or variable frame rates often trigger the unavailable status even when the token is valid. Create a short checklist that every team member follows: resolution at 1080x1920 for Reels, file size under 4 GB, and duration between three and ninety seconds. Store the checklist in the shared drive so new contributors do not introduce non-compliant files.

When an asset fails the check, replace it rather than attempt to repair the container. Re-encoding on the fly inside the scheduler has caused the same error code to repeat across multiple accounts. Instead, export again from the editing software with the verified preset and re-upload to the asset folder.

Set up automated monitoring alerts

Connect the platform’s webhook endpoint to your team chat so any new “account unavailable” event creates a thread with the exact error payload. Configure the alert to include the account name, the scheduled time, and a direct link to the post in Compose. This removes the need to poll the dashboard every hour and surfaces problems while the token is still fresh.

Add a secondary alert that fires when token expiry is within seven days. The notification lands in the same channel and tags the person responsible for renewal. Because tokens are issued through the Meta Business API, the seven-day window gives enough lead time to complete the login flow without interrupting the queue.

Test the webhook once a month by forcing a test publish to a sandbox account. Confirm the message arrives with the correct metadata before relying on it during production campaigns.

Document recovery procedures for persistent issues

Maintain a shared runbook that lists every step taken when the unavailable flag remains after a token refresh. Record the date, the account ID, the exact response from the API, and the resolution. Over time the runbook reveals patterns such as certain business categories triggering extra review or specific caption phrases being blocked.

When the runbook entry shows the same account failing three times in one week, move the profile to a manual-only workflow for fourteen days. During that period publish only through the native Instagram app and note any restrictions that appear in the business dashboard. After the cooling period, re-add the account through Platform Settings and monitor the first five scheduled posts at fifteen-minute intervals.

Include contact notes for Meta support in the same document. Reference the support ticket number and the date the case was opened so anyone on the team can follow up without repeating the initial diagnosis.

Coordinate cross-platform scheduling to avoid conflicts

When Instagram is restricted, shift priority content to Threads or X using the same caption file. Export the UTF-8 text once and import it into the alternate destination inside Compose. This keeps the publishing cadence while the Instagram token issue is resolved.

Create a simple rule in the scheduler that blocks any Instagram post from running within thirty minutes of a Threads post from the same account. Overlapping activity windows have produced additional rate-limit flags even after the token was renewed. Review the combined calendar every Friday and adjust the following week’s queue accordingly.

Track the number of cross-platform handoffs in a monthly spreadsheet. If more than twenty percent of Instagram posts are rerouted, schedule a dedicated review of the token scopes and activity limits before the next billing cycle.

Establish a weekly token health check

Schedule a recurring task every Monday morning inside the Team Calendar to inspect all connected Instagram accounts. Open the token overview panel and note the issued date next to each profile. Any token older than 45 days receives a renewal flag that appears in the same row. Assign the renewal step to the team member listed under account owner so the task does not linger past Wednesday.

During the check, also review the last successful publish timestamp. If more than four days have passed without activity, force a test post to a hidden test Reel using a 15-second clip. Record whether the test clears without an unavailable response. This single data point often reveals scope drift before it affects live campaigns.

Build a fallback content library

Create a dedicated folder labeled fallback-instagram inside the shared asset drive. Populate it with 12 Reels and 8 carousels that use only in-house audio tracks and square-safe aspect ratios. Each file carries a one-line note in its filename that states the exact caption length and whether it contains any text overlay.

When an account enters the unavailable state, the scheduler automatically pulls the next item from this folder instead of pausing the queue. The rule is set once in Workflow Rules and applies to every profile. Team members update the library on the first Friday of each month by replacing the oldest four assets with fresh versions that still meet the H.264 checklist.

Review API response codes in detail

The Meta Business API returns several numeric codes under the unavailable banner. Map each code to an action in a shared reference sheet stored at /docs/instagram-codes.md.

Code	Typical cause	First action	Escalation path
190	Expired or revoked token	Re-authenticate in Platform Settings	Open Meta support ticket
10	Permission missing	Add instagram_content_publish scope	Re-run token exchange
368	Rate limit hit	Delay next 10 posts by 40 minutes	Review activity log for patterns
24	Media format rejected	Replace file and re-encode to H.264	Update asset checklist

Store the sheet as a living document so new codes discovered during incidents are added the same day. Every entry includes the date it was last observed and the account ID involved.

Coordinate with external compliance tools

Connect the FlixySocial webhook to a lightweight compliance script that scans captions for restricted phrases before they reach the queue. The script lives in the same repository as the scheduling rules and triggers a hold status visible in Compose. When the scan flags a caption, the item moves to a review lane that requires manual approval from two team members.

Run the script against the prior 30 days of published captions once per quarter. Export the results as a CSV and compare flagged phrases against actual Meta policy updates listed in the business help center. Adjust the script keywords only after confirming the change in official documentation to avoid unnecessary holds.