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).β¦