X Failed to Send Your Post? Here's What Actually Causes It

Worth separating two problems that get searched interchangeably: a post that will not publish is not the same as a DM that will not send. Different limits, different causes, different fixes. If your DMs are the problem, start here instead.

For posts, there are seven realistic causes.

1. You hit the daily post limit

X publishes a cap of 2,400 posts per day for standard accounts. That sounds unreachable until you learn that replies and reposts count toward it, and that there is an unpublished hourly throttle underneath it that most people hit long before the daily figure.

Confirms it: every post fails, and you had been unusually active, particularly replying.

Fix: stop for a few hours. The window rolls rather than resetting at midnight, so capacity returns gradually.

2. Duplicate content

X blocks identical and near-identical posts. This catches more people than it should, because it applies across time rather than just consecutively. Posting the same line you posted last week can fail.

Confirms it: one specific post fails while others publish fine, and you have posted something similar before.

Fix: rewrite it rather than retrying. Changing a few words is usually enough. Repeatedly posting near-duplicates is itself a spam signal, so this is worth taking as feedback rather than an obstacle.

3. A link X does not like

Shortened links are the usual trigger, along with domains X has seen used in spam.

Confirms it: the same post publishes with the link removed.

Fix: use the destination domain directly instead of a shortener. If a legitimate domain is being blocked, putting it in a reply rather than the main post sometimes works.

4. Media that did not upload

The post looks ready but the image or video never finished uploading, often on a weak connection.

Confirms it: text-only posts publish fine.

Fix: remove the media, confirm the text posts, then re-add it. Check the file is within X's size and format limits.

5. Your account is restricted

A restricted account can fail to post alongside quieter symptoms.

Confirms it: run our shadowban test to see whether your account and posts are still returned by X's search index. If they are not, publishing problems and visibility problems have the same root.

Fix: stop whatever triggered it for 48 hours, behave normally for a week. No appeal, because no human decided it.

6. Over the character limit

Standard accounts get 280 characters; Premium tiers get considerably more. Pasting long text from elsewhere is the usual way people cross it without noticing, especially when invisible characters come along with it.

Fix: shorten it, or split it into a thread.

7. X is down, or your app is stale

Outages happen. So does an app version old enough to be rejected.

Confirms it: it fails everywhere including the web, and others are reporting it.

Fix: update the app, or wait.

The check that saves the most time

Ask one question: does every post fail, or just this one?

• Every post points at your account: a limit, a restriction, or an outage.
• Just this one points at the content: duplicate text, a link, media, or length.

That single split resolves most cases without any further troubleshooting.

If you also run outreach from this account

Posting failures and DM failures often show up together, because both are downstream of the same behavioural throttling. An account being pushed hard on DMs will start seeing post failures too.

The underlying fix is the same: slow down and spread activity out. Speed trips X's limits before totals do, which is why an account doing a moderate amount steadily outlasts one doing the same volume in bursts. For the DM side specifically, our DM limit calculator gives a sustainable daily rate, and X's rate limits covers every cap the platform enforces.

Short version

Posts and DMs fail for different reasons, so do not apply DM advice here. Ask whether every post fails or just one: every post means a limit, a restriction or an outage; one post means duplicate text, a link, media or length. Rewrite rather than retry when it is content, and wait rather than retry when it is a limit.