# How to Schedule a Thread on X (and What Happens at Post Time)

Published: 2026-10-22

**Key takeaways:** X documents scheduling single posts, not threads, so use a scheduler that publishes the parts as a reply chain. PostBoost checks every part before the first goes out, and if a part fails, Retry continues from that part instead of posting the thread twice.

**Short answer:** X's Help Center explains how to schedule a single post, in the web composer and in X Pro, but it doesn't describe scheduling a whole thread, and guides that claim it works contradict the ones that say it doesn't. The dependable way is a scheduler that publishes the parts itself. In PostBoost: create a post, select your X account, click **Add Post** for each part, then **Schedule**. At the set time the parts go out as a reply chain, in order.

The rest of this guide covers the part most guides skip: what happens at post time, and how to fix a thread that stops halfway.

## Can X schedule a thread on its own?

Not in a way you can count on. X's own documentation covers scheduling a post: compose it, pick a date and time, confirm. X Pro, the multi-column dashboard that comes with a paid X subscription, adds a Scheduled column where you can see and edit scheduled posts. Neither page describes scheduling a thread.

Third-party guides don't settle it either: most say the native scheduler takes one post at a time, while a few describe adding parts in the web composer and scheduling them together. If you want to try, schedule a test thread and then open your scheduled posts list to check that every part is there before you rely on it.

A scheduler avoids the question. It stores the parts and, at the scheduled time, publishes the first post and then each next one as a reply to the one before. That's what a thread is on X: a chain of replies by the same account.

## Before you schedule: write the parts

Each part gets its own limit: **280 characters** on a standard account, with every link counted as 23 and every emoji as 2, from [X's counting rules](https://docs.x.com/resources/fundamentals/counting-characters). If you're starting from a long text, paste it into the free [X thread maker](/tools/x-thread-maker): it splits at paragraphs and sentences, never mid-word or mid-link, and numbers the parts within the limit. [How to turn a blog post into an X thread](/learn/blog-post-to-x-thread) covers the writing side: one idea, one point per post, opener last.

## Schedule an X thread in PostBoost

1. Create a post and select your X account.
2. Write the first post. Click **Add Post** to add the next part, and repeat for each part, in order. The composer counts each part against X's limit separately.
3. Click **Schedule** and choose a date and time. The time zone shows next to the time.
4. Click **Done**, then **Schedule**.

The thread appears in the calendar as one post. Prefer a fixed rhythm? **Add to Queue** puts it into your X account's next free slot of the posting schedule instead.

**Posting the same update to Facebook, Instagram or LinkedIn too?** Those networks don't take a thread (Facebook and Instagram turn the second item into a first comment), so give X its own version: click the **+** (Create version) next to the version tabs, choose your X account under **Create version for**, and add the thread parts in that version. The other networks keep their single post.

**Not sure when?** The free [best time to post tool](/tools/best-time-to-post) puts three large studies' X times side by side. Once your account has published enough posts with imported statistics, the **Schedule** panel's **Best times to post** section suggests times from your own results.

## What happens when the thread goes out

At the scheduled time PostBoost publishes the first post, then each next part as a reply to the part before it, one right after the other. Three things are worth knowing:

- **Every part is checked before the first one goes out.** You can keep editing a scheduled thread until it starts publishing, so PostBoost checks all parts against X's rules again right before posting. If one has become too long, nothing is published and the post shows the reason. Without that check, a thread would go live up to the bad part and stop there.
- **Each part's ID is saved as soon as it's live.** That's what makes a retry safe (next section).
- **One thread, one entry.** In the calendar and in the post's **Delivery** tab the thread is one post; once it's live, **View on platform** opens it on X.

## When a thread stops halfway, and how to finish it

Once the first part is live, a problem with a later part can't be undone by stopping, so PostBoost doesn't try. Say part 3 of 5 is refused by X, or the connection drops: parts 1 and 2 stay live, and the post is marked as failed for your X account. Open the post and go to the **Delivery** tab. It shows the error and a line such as **2 of 5 parts published**.

Fix the cause (for example, reconnect the account if its access expired), then click the retry button next to the account. Its tooltip reads **Continue publishing**. Publishing continues from the part that failed: part 3 is posted as a reply to part 2, then parts 4 and 5 follow. The parts already published stay as they are and are never posted a second time, so a retry can't leave you with a duplicate opener.

The API does the same with [retryPostAccount](/docs/api/retry-post-account): `POST /{workspaceUuid}/posts/retry/{postUuid}/{accountUuid}`. It answers `422` if the account didn't fail or the post is still publishing. To see where a thread stands, fetch the post: each account carries `publish_status` (`pending`, `publishing`, `published` or `failed`) and `published_parts`, the number of parts that are live.

## Schedule an X thread with the API

Every item after the first in a version's `content` array is published as the next part of the thread. Find the X account's `id` with `GET /{workspaceUuid}/accounts`, then:

```bash
curl -s -X POST "https://postboost.co/app/api/$WORKSPACE_UUID/posts" \
  -H "Authorization: Bearer $POSTBOOST_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "accounts": [12],
    "schedule": true,
    "date": "2026-10-29",
    "time": "14:00",
    "timezone": "Europe/London",
    "versions": [{
      "account_id": 0,
      "is_original": true,
      "content": [
        { "body": "How we schedule product threads on X without a broken chain. 1/3" },
        { "body": "Every part is checked against the 280 limit before the first one goes out. 2/3" },
        { "body": "If a part fails, retry continues from that part. Full guide: https://example.com/threads 3/3" }
      ]
    }]
  }'
```

If any part breaks X's rules, for example 281 characters, the call is refused with `422` and nothing is created; the error names the network and the part, such as `X → Post #2 - Maximum of 280 characters allowed.` Leave out `schedule`, `date` and `time` to save a draft. The `Idempotency-Key` makes a retried request safe, and the API refuses a post that repeats one created for the same account in the last 24 hours unless you send `allow_duplicate` ([guardrails](/docs/guardrails)). Every field is in [createPost](/docs/api/create-post); the free [API request builder](/tools/social-media-api-request-builder) writes a single-post call in your language that you can extend with more `content` items.

## Schedule an X thread from Claude or ChatGPT

With the PostBoost connector added to your AI assistant, ask in plain words:

> Split this announcement into a three-part X thread, under 280 characters per part, link only in the last part, and schedule it for Thursday at 14:00 London time.

The assistant finds your X account with `list-accounts`, then calls `create-post` with the three parts as content items, `schedule` set to `scheduled`, a `scheduled_at` and the `timezone`. Ask it to save a draft instead if you want to read the thread first. Setup: [How to schedule social media posts with Claude](/learn/schedule-social-media-posts-with-claude).

## What a thread costs on your X allowance

X bills every post created through its API, and a post with a link costs about 13 times more. In PostBoost, each part of a thread counts as one X post toward your plan's monthly X allowance, and a part with a link (even a bare domain such as `example.com`) also counts as a link post. A five-part thread with one link in the last part uses five X posts, one of them a link post. The allowance is tracked but not enforced yet; the [X policy](/docs/x-policy) has the numbers per plan. The free [X API cost calculator](/tools/x-api-cost-calculator) shows what the same volume would cost at X's own prices.

## Checklist before you hit Schedule

- Every part fits 280, numbers included. The [character counter](/tools/social-media-character-counter) counts links and emoji the way X does.
- The parts are in the right order in the composer, or in the X version if the post also goes to other networks.
- The link is in the last part only.
- The time is set in the time zone you mean.
- After it goes out, glance at the **Delivery** tab: **Published** means every part is live.

Ready to try it? [Create a free PostBoost account](/app/register), connect X and schedule your first thread. Plans are on the [pricing page](/#pricing).

## Do this in PostBoost

- [Publish and schedule](https://postboost.co/features/publish): Write one post, adjust it for each account, then schedule it, add it to your queue or publish now.

## Free tools for this guide

- [X thread maker: split long text into numbered posts](https://postboost.co/tools/x-thread-maker): Split long text into numbered posts for X, Threads, Bluesky or Mastodon. Never cuts a word or a link. Free, no signup, runs in your browser.
- [Best time to post on social media, by network and weekday](https://postboost.co/tools/best-time-to-post): Best times to post on Instagram, Facebook, LinkedIn, X and TikTok by weekday, from Sprout Social, Buffer and Hootsuite, side by side with sources.
- [Social media API request builder](https://postboost.co/tools/social-media-api-request-builder): Build a create-post request for the PostBoost social media API and copy it as curl, Python, Node.js, PHP, Go, Ruby, Java, C#, Rust or the CLI.

## FAQ

### Can you schedule a thread on X without a third-party tool?

X's Help Center explains how to schedule a post in the X web composer and in X Pro, but it does not describe scheduling a whole thread, and third-party guides contradict each other on whether it works. If you try it natively, check your scheduled posts afterwards to see whether every part was saved. A scheduler that publishes the parts itself is the reliable option.

### How do I schedule an X thread in PostBoost?

Create a post, select your X account, write the first post and click Add Post for each next part. Then click Schedule, pick the date and time, click Done and then Schedule. PostBoost publishes the parts as a reply chain, in order, at that time.

### What happens if one post of a scheduled thread fails?

The parts before it stay live and the post is marked as failed for that account, with the error and a count such as "2 of 5 parts published". Click the retry button (its tooltip reads Continue publishing) in the post's Delivery tab. Publishing continues from the part that failed; the parts already published are not posted again.

### Can I edit a scheduled X thread?

Yes, until it starts publishing. Open the post from the calendar, change, add or remove parts, and it keeps its scheduled time. Right before publishing, PostBoost checks every part again, so a part that became too long stops the whole thread instead of leaving it half posted.

### How long can each post in a scheduled X thread be?

280 characters per part on a standard account, with every link counted as 23 and every emoji as 2. PostBoost allows up to 25,000 characters per part for accounts X reports as verified, but threads are usually written as short parts anyway.

### Does each part of a thread count toward my X allowance?

Yes. Each part is one X post toward your plan's monthly X allowance, and a part that contains a link also counts as a link post. Putting the link in the last part only keeps a thread cheapest. The allowance is tracked but not enforced yet.

## Sources

- [X Help Center: how to use X Pro (scheduling posts)](https://help.x.com/en/using-x/how-to-use-x-pro)
- [X Help Center: how to create a thread on X](https://help.x.com/en/using-x/create-a-thread)
- [X developer docs: counting characters](https://docs.x.com/resources/fundamentals/counting-characters)
- [PostBoost docs: X (Twitter) policy](https://postboost.co/docs/x-policy)
- [PostBoost docs: guardrails](https://postboost.co/docs/guardrails)
- [PostBoost API reference: createPost](https://postboost.co/docs/api/create-post)
- [PostBoost API reference: retryPostAccount](https://postboost.co/docs/api/retry-post-account)

Canonical: https://postboost.co/learn/how-to-schedule-a-thread-on-x
