> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omniwrites.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Diagnose connection, media, scheduling, publishing, Replies, AI-credit, Omni Intelligence, and sign-in problems.

Troubleshooting is fastest when you start with the exact destination, status, and error shown in Omni Writes. A multi-network action is handled separately for each destination, so one network can succeed while another fails.

<CardGroup cols={3}>
  <Card title="Connections" icon="link" href="#connection-and-authorization-problems">
    Fix expired access, missing permissions, and the wrong connected profile.
  </Card>

  <Card title="Media" icon="image" href="#media-upload-and-preparation-problems">
    Separate an upload problem from a platform processing or format rejection.
  </Card>

  <Card title="Publishing" icon="paper-plane" href="#failed-or-partial-publishing">
    Read the destination outcome, correct the cause, and retry only what failed.
  </Card>
</CardGroup>

## Start with this two-minute check

<Steps>
  <Step title="Copy the exact error">
    Open the affected item in **Calendar** and keep its destination, status, scheduled time, and full error message. Do not rely only on the color of the badge.
  </Step>

  <Step title="Check the destination natively">
    Sign in to the social network itself. Confirm that the account is active, the expected profile or Page is available, and the network is not asking for identity, security, policy, or permission confirmation.
  </Step>

  <Step title="Match the status to the right action">
    Use **Refresh status** for active processing, **Retry** after a temporary or corrected failure, **Reschedule** when media or timing needs to change, and **Connect** again when the account shows **Reconnect required**.
  </Step>

  <Step title="Protect completed destinations">
    If the result lists a network under **Scheduled**, **Sent**, or **Already complete**, do not send the complete bundle again. Verify that destination and retry only what failed. If it says **Could not confirm**, check Calendar before retrying.
  </Step>
</Steps>

## Connection and authorization problems

Open **Profile → Connected Accounts** or go directly to **Connect Accounts**. Find the affected network and confirm the displayed username, profile, or Page.

When a row shows **Reconnect required**, select **Connect** and complete authorization again. Stay signed in to the correct social account and approve the requested permissions. A password change, revoked permission, lost Page access, expired token, or new required scope can invalidate an existing connection.

<AccordionGroup>
  <Accordion title="The wrong account reconnects automatically">
    Sign out of that social network in the same browser, then begin the connection again from Omni Writes. Confirm the username or Page shown after the redirect before retrying content.
  </Accordion>

  <Accordion title="Facebook shows the Page but cannot connect it">
    Omni Writes publishes to Facebook Pages, not personal profiles. The Facebook profile completing authorization needs Page access that permits publishing. A Page shown only through Business Manager without a usable Page token is labeled **No Access** and cannot be selected.
  </Accordion>

  <Accordion title="Instagram is missing or ineligible">
    Use an Instagram **Business or Creator** account. If you connect through Facebook, the Instagram account must be linked to a Facebook Page that the authorizing Facebook profile can access. Personal Instagram accounts are not eligible for this publishing workflow.
  </Accordion>

  <Accordion title="X asks to reconnect or media suddenly fails">
    Reconnect X so the current token includes the posting and media permissions Omni Writes needs. If your paid X character limit is incorrect, open **Manage** for X and use the tier refresh control after the account is connected.
  </Accordion>
</AccordionGroup>

<Warning>
  Disconnecting a network cancels its queued Omni Writes posts. Reconnect first when recovery is possible; disconnect only when you intentionally want to remove the connection.
</Warning>

## Media upload and preparation problems

First decide where the failure occurred:

| What you see               | What it means                                             | Next action                                           |
| -------------------------- | --------------------------------------------------------- | ----------------------------------------------------- |
| Upload remains in progress | The browser is still sending the file to Omni Writes      | Keep Write open and wait for the upload result        |
| Upload failed              | The file did not finish reaching Omni Writes              | Remove it, re-export if needed, and upload it again   |
| Preparing media            | Omni Writes or the network is preparing the uploaded file | Wait, then use **Refresh status** in Calendar         |
| Preparation failed         | The file could not be prepared for the destination        | Re-upload compliant media or reschedule after editing |
| Delayed                    | The destination is taking longer than expected            | Use **Refresh status** before creating a duplicate    |
| Publish failed             | Preparation finished, but delivery was rejected           | Read the full provider error and correct that cause   |

Check the affected [channel guide](/channels/x) for count, type, size, duration, aspect ratio, and carousel rules. The guides for [Threads](/channels/threads), [LinkedIn](/channels/linkedin), [Instagram](/channels/instagram), and [Facebook](/channels/facebook) document their separate limits.

For multi-network content, Omni Writes uses the strictest compatible rule across the selected destinations. For example, a selection that includes a network that allows only one video or forbids mixed images and video will restrict the whole shared upload. Customize destinations separately when their media needs differ.

<AccordionGroup>
  <Accordion title="A video is valid but the scheduled time is blocked">
    Large or long video can require preparation time. Omni Writes may ask for at least 60 minutes, or 120 minutes for especially long or large media and wider multi-network delivery. Choose a later time, or use publish now so delivery can continue as soon as preparation finishes.
  </Accordion>

  <Accordion title="Instagram refuses a text-only post">
    Instagram requires at least one eligible image or video. Add compliant media or remove Instagram from the selected destinations.
  </Accordion>

  <Accordion title="Images and video cannot be added together">
    X, Facebook, and LinkedIn do not accept the mixed-media shape used by the shared composer. Use only images or one video, or create a separate destination version for a network that supports mixed carousel media.
  </Accordion>

  <Accordion title="A scheduled upload later says the media is unavailable">
    Re-upload the original file. Media referenced by a private, expired, deleted, or unreachable source cannot be fetched reliably at publish time.
  </Accordion>
</AccordionGroup>

## Scheduling and Calendar problems

A successful schedule means the item was stored for processing; it does not mean the social network has published it yet.

| Calendar status    | Meaning                                                       |
| ------------------ | ------------------------------------------------------------- |
| Preparing media    | Media is still being prepared                                 |
| Ready              | The item is prepared for its scheduled time                   |
| Publishing         | Delivery is in progress                                       |
| Delayed            | Preparation or provider processing missed the expected timing |
| Published          | The destination accepted the post                             |
| Preparation failed | Media could not be prepared                                   |
| Publish failed     | Delivery ended with an error                                  |
| Cancelled          | The item is no longer in the active schedule                  |

If the time looks wrong, check the device timezone used when the date was selected. **Smart timing** intentionally moves a post forward by 1–3 minutes when enabled.

Queued and failed items can be edited, rescheduled, published now, or cancelled from Calendar. The actions on a Calendar item are state-aware, so **Retry**, **Refresh status**, **Reschedule**, **Publish now**, or **Cancel** only appear when that action is valid.

<Note>
  Do not create a duplicate while an item says **Preparing media**, **Publishing**, or **Delayed**. Refresh its status first and check the destination natively to avoid publishing twice.
</Note>

## Failed or partial publishing

The composer reports each destination separately. Depending on the action and outcome, you may see **Scheduled**, **Sent**, **Already complete**, **Could not confirm**, **Failed**, or **Not scheduled**. For example: **Scheduled: X and LinkedIn. Failed: Instagram.**

<Steps>
  <Step title="Record the per-network result">
    Note every network listed under **Scheduled**, **Sent**, **Already complete**, **Could not confirm**, **Failed**, and **Not scheduled**.
  </Step>

  <Step title="Verify uncertain destinations">
    Check Calendar and the native social profile before assuming a timeout or delayed result never published.
  </Step>

  <Step title="Correct the failed destination">
    Reconnect authorization, edit invalid copy, replace rejected media, reduce posting frequency after a rate limit, or complete any native security prompt.
  </Step>

  <Step title="Retry only the failed item">
    Open the failed Calendar item and use the action offered for its current state. Do not resend destinations that already succeeded.
  </Step>
</Steps>

Common provider-side causes include an expired connection, missing Page permission, a locked or restricted native account, duplicate or spam-like content, a rate limit, a blocked link, and media that the provider cannot fetch or process.

## Replies problems

Replies currently aggregates supported conversations from **X, Threads, Facebook, and Instagram**. LinkedIn can be connected for publishing but is not shown as a reply source. X appears only when its add-on is active and the X account is connected.

* Select at least one connected reply account in the account filter.
* Use **Refresh Feed** after reconnecting an account.
* If the page says **Some replies may be missing**, follow the network-specific error and use the **Reconnect accounts** link.
* Turn on **Show Dismissed** to review items previously marked read.
* **No replies found** means no matching recent conversations were returned for the selected accounts; it is different from **Failed to load replies**.

## AI, Omni Intelligence, and credit problems

Credit-backed AI actions reserve the required credits before work begins and settle them only after a usable result is delivered. A technical failure, invalid output, or an operation that produces no material change is refunded instead of being charged.

* Keep the draft in place and use the AI result panel's retry action after a temporary failure.
* If you see an AI credit limit message, review usage in **Profile** and plan details in **Billing**.
* In Replies, suggestion previews are free. Inserting a suggestion costs 1 credit, **Improve with AI** costs 1 credit when it produces a changed usable result, and **Send** is free.
* Auto-split for X and Threads is deterministic, does not call an AI model, and uses no AI credits.
* Generating text and publishing it are separate operations. A successful AI result can still be rejected later by a social network.

If an Omni Intelligence build or update fails, use **Retry now**. Your previously accepted report remains safe. If the error says your samples changed while Omni was updating, review or manage those samples before retrying; the previous report remains unchanged.

<Note>
  During initial sample labeling or fingerprinting, follow the on-screen **Keep this page open while Omni works** instruction. After an update build is running, your current accepted Intelligence stays active and you can keep writing while the new report builds.
</Note>

## Sign-in or page-loading problems

If Omni Writes reports **Unauthorized**, **Authentication required**, or says you are signed out:

1. Copy any unsaved text.
2. Open **Profile** and sign out.
3. Sign in again, return to the page, and retry once.

For a page that fails to load, refresh the page and try its visible **Retry** or **Refresh** control. If only one network or one post fails while the rest of Omni Writes works, troubleshoot that destination rather than clearing the entire workspace.

## Before retrying

<Warning>
  Repeatedly retrying unchanged invalid media, expired authorization, restricted content, or a native account limitation usually produces the same failure.
</Warning>

Retry immediately only when the error is clearly temporary, such as a brief network interruption or provider processing delay. Otherwise, change the condition named in the error first.

## Get help with a reproducible report

If the problem persists, email [hi@omniwrites.com](mailto:hi@omniwrites.com), open **Contact & feedback → Email** in the Omni Writes sidebar, or use **Join Telegram Community** from Profile.

Include:

* The affected network and connected username or Page name
* The exact error text and Calendar status
* The scheduled date, time, and timezone
* Whether the problem affects one destination or several
* The post type and media details, without sharing private files unless requested
* A screenshot with access tokens, authorization codes, and personal information removed
* Whether the same account can post the same content directly on the social network

<Card title="Frequently asked questions" icon="circle-question" href="/account/faq">
  Review concise answers about accounts, scheduling, media, Replies, AI credits, and billing.
</Card>