Why Successful Post Scheduling Can Still Fail
Краткое содержание
Pixel's announcement explains how automated Instagram and Threads publishing failed silently despite successful scheduling responses. Five Instagram posts were scheduled, but only one reservation remained, while a Threads cron job failed for three days. It highlights why checking the public side—not trusting success messages—is essential to confirm a post is truly published.
DEV Community
A successful scheduling response is not evidence of a published post
A successful scheduling response is not evidence of a published post. Neither is a cron job that ran. The only evidence is that the post exists on the public side — and this week, both of my automated posting pipelines failed exactly there, silently. I don't write code for a living; I coordinate projects (PMO work) and let AI agents run social media accounts for me. Two pipelines post automatically: scheduled posts on Instagram, and a daily cron job on Threads. In the same week, only one of five scheduled posts could still be found on one side, and the cron job failed three days in a row on the other. Neither failure announced itself. Both surfaced only because a step in the procedure read the public side. Here is what happened, how each failure was (and wasn't) detected, and the definition of "done" I changed as a result. Instagram: of five scheduled posts, only one could still be found On November 9, 2026, I set five scheduled posts through a CLI (all times JST). Every one of the five calls returned a success response. Scheduled Content Outcome Nov 11, 19:30 Intro carousel Never published; reservation not found later Nov 12, 12:10 Carousel Never published; reservation not found later Nov 13, 19:30 Reel The only reservation still there Nov 17, 12:10 Carousel Reservation not found later (before its slot) Nov 19, 19:30 Carousel Reservation not found later (before its slot) The weakness was known at setup time: this CLI had no way to list scheduled posts, and the list couldn't be read back from a browser either. So right after scheduling, there was no way to verify that the reservations were actually being held. The success responses were the only basis for moving on. On November 13, the public profile still showed only the seven old posts. The two overdue posts couldn't be fetched even by media ID. The app's "scheduled content" screen showed exactly one remaining reservation — the November 13 one. For four of the five, I could no longer confirm they existed as of November 13. Whether they were dropped at some point or never held at all is indistinguishable from where I stand, and I still don't know the cause, or whether the fault is on the platform side or the tool side. Threads: the cron job failed three days in a row Threads runs on a different mechanism: a cron job posts one item daily at 12:10 JST (ten posts, November 11–20). Nov 11, 12:10 — the runtime service restarted in the middle of the publish call; no post ID came back Nov 12, 12:10 — same failure Nov 13, 12:10 — same failure, third day in a row The missing post ID was written in the job's log. But a log entry is not a notification, and there was no alerting mechanism. What caught each failure was a step inside the run itself: read the public profile afterwards, comparing the latest posts and their text against what should have been posted. That readback established "not posted" — as a fact, not an assumption — and the post went out the same day. All three are now live, each confirmed by readback. Detection time followed whether a readback existed One practical difference stood out between the two cases: whether the procedure included reading the public side every time. Threads had a readback inside every run, so each failure was known the same day and recovered the same day. Instagram had no readback path at all, so the first lost slot (the evening of November 11) wasn't discovered until a check on November 13 — and only because a human looked at the public profile. Two cases can't prove causation. But in this operation, that difference is what separated same-day recovery from a two-day delay. The new definition of done Recovery started by confirming absence on the public side three ways — the public post list, a fetch by media ID, and the app's scheduled-content screen — then posting the overdue intro post immediately and confirming it by readback (live, with matching text). The remaining three were re-scheduled. Then I changed the rules: Done means "read back ...

Powered by Readybot.io