Autonomous Video Studios
HomePART II · The original programme
CHAPTER 9 · NEW SINCE THE FIRST EDITION

Every failure has a lever

A platform refusing a post is a normal day's work: a token expires, an account needs a check, a service times out, a pay-per-use balance runs out. What matters is that nothing is lost, that every attempt is on the record, and that whatever needs a person is in front of them with the button that fixes it — in the same place the problem is shown.

Every failure has a lever — in the original's portal and in ChannelForge
A post is refused

any platform, any project: a token, a checkpoint, a timeout, missing credits

The ledger

every attempt, append-only, one line each; 16 reasons; read every five minutes

The history page

Needs you · Open now · History · By day · Reasons; a CSV for the records

A lever per row

reconnect · check now · refresh · retry one or a group, spaced like a person

Where the fix is elsewhere

a direct link (X credits, a Meta check) and a 'done — retry now' button

↺ the publisher tries again — now, or queued at a human-looking gap — and the ledger records how it ended
Figure 16. A failed post's way back. The publisher keeps retrying on its own; what it cannot fix appears on one page with a lever beside it.

The ledger#

Since 13 November every failed publishing attempt, in every project and on every platform, is written to an append-only ledger: one line per attempt, with the platform's own words, the account, the episode, a reason from a fixed list of sixteen, and how it ended. Backfilled from the records, the history goes back to 25 October: 1,029 failed attempts on 521 posts, of which 490 are resolved. 721 of the attempts are X waiting for its API credits; of the rest, the biggest kind is Instagram saying it could not process a video, which led to the fetch-first upload described in the previous chapter.

ReasonFailed attemptsWhat it means
X credits721X's pay-per-use balance is used up: posts wait, nothing is lost
Media processing119the platform could not process the video; most go out on a retry
Account unlinked81an Instagram account was unlinked from its Page: the owner relinks it
Timeout or network36the platform did not answer in time: retried with backoff
Meta checkpoint10Meta asks the account's owner to confirm it in the app
Other62tokens, rate limits, posts that may already be live
Every failed publishing attempt of the original programme, 25 October – 14 November 2026, by reason. One attempt is one line: a retry that the platform refuses again is a second attempt, never a duplicate.

The page, and the levers#

The portal's Failures page reads the ledger every five minutes and shows it five ways: what needs you (grouped by account), what is open now, the full history with filters and a CSV, by day and by reason. Every row and every group has a lever: Reconnect the account through its sign-in, Check now, refresh a Meta or LinkedIn token, or retry one post or a whole group — spaced like a person would, stopped at the platforms' daily caps. Where the fix can only happen elsewhere — topping up X, confirming an account in Meta's app — the lever is a direct link and a 'done, retry now' button. The morning report e-mailed at 08:00 has a section on the last day's failures.

ChannelForge has the same, for every workspace: a Failures tab under Publishing for its members, and an admin page for the operator, with the same levers and the same rule — a group retry is spaced, capped and never posts in a burst.