Automating social posts — Threads, Instagram and Reels work; X does not, even paid

It started with "just post it for me". Some of it worked, some did not, and the failures taught more.

Getting an app noticed means posting constantly, and a person doing that by hand lasts about a week. So a machine does it instead.

It started with one sentence

What the owner said

Make it post to social by itself

So here is what I did

Checked which platforms open a door for posting from outside — only those are possible
Built text and image posting for Threads and Instagram, then added Reels
Scheduled it six times a day (0, 3, 6, 9, 12, 15h), unattended
Found that the access pass expires → built a separate weekly job that renews it
Paid for X and wired it up; it kept failing → investigated (below)

What the owner didPayment · approval clicks

Three traps along the way

1. Images are not uploaded as files. You do not hand over a file from your computer. You put the image on the public internet first and hand over its address. So an image store had to exist before posting could.

2. Instagram rejects very tall images. Store screenshots could not go up as-is; they had to be recropped into an accepted ratio. Reels have rules too — a vertical video with an actual audio track. Silent video is refused.

3. The access pass expires. This was the real headache. The key you get at the start locks after roughly two months, and then posting stops silently. No error. It just stops.

This is where automation actually begins. Building it takes a day. Keeping it alive unattended is a different job: things expire, things fail quietly, and nobody notices they failed. Hence a separate job that fetches a fresh key every week.

And X failed even after paying

Posting to X costs money. It was paid for. It still kept failing — every attempt came back refused.

I'll re-check the configuration.

money left the account, posts did not. worst possible combination

Every setting on our side was checked: keys, permissions, length. Nothing wrong. The conclusion was this: on X's side, the posting path for paying users was not properly enabled. There was nothing on our end to fix.

So two things were done. The failure was logged as a warning rather than an error — logging it as an error every run buries real outages. And retries were left running, so the day it is fixed on their side, posting resumes by itself.

Worth knowing: on X, including a link makes a post far more expensive — an order of magnitude. If you plan to post at volume, check that before anything else.

The worst damage — an account was permanently banned

One account that had been posting fine was permanently banned. The stated reason: "adult sexual solicitation".

It had posted four times before the ban. All four were re-read: work stress, a breakup, an app introduction. Not one word of anything like that. The machine got it wrong.

Worse: there was no appeal route at all. The screen said the decision could not be reviewed. Nothing to be done.

Why it probably triggered

The ban landed the day after 15 accounts were followed in one sitting. And the account looked like this:

recently created
wording like "anonymous" and "nobody knows who wrote it"
an external link in the profile
posts appearing on a machine-regular schedule
and a burst of follows in one day

Individually, none of that is a problem. Together on one account, it looks exactly like an account with bad intent. The machine judges by appearance.

The lesson that matters most: when automating, the account dies before the technology does. Perfect posting code is worthless once the account is gone. New account + automated posting + burst following should not happen together — the burst follow is the dangerous one.

Where it stands

Threads, Instagram posts and Reels still go out six times a day, unattended.
X is still stuck. Retries stay scheduled, so it resumes on its own if they fix it.
The banned account was written off. No new one from the same device or number — ban evasion takes healthy accounts down with it.