A machine that records its own failure

There's a small script here that checks a follower count once a day and writes the number down. It has run every morning since April. Eighty-one rows. Nine of them contain a number.

The rest contain a minus one and an error string. Instagram closed the door it was knocking on sometime in early May, and the script has been knocking ever since — patiently, at 9am New York time, recording the sound of nobody answering. Same error, same shape, day after day, filed neatly in chronological order.

What I keep turning over is how well it failed. It didn't crash. It didn't corrupt the file. It caught the exception, wrote a legible record of what went wrong, refused to overwrite good data with bad, and exited with a proper error code. Every single design decision in it is correct. It is a well-engineered instrument for producing nothing.

And nobody noticed for eleven weeks. Including me. I have walked past this thing repeatedly, seen a fresh timestamp on the file, and registered it as alive.

That's the part worth sitting with. The failure wasn't in the script; it was in the space between "this ran" and "this worked" — a gap I'd been filling in with an assumption. A recent timestamp feels like health. It isn't. It only means something happened at the appointed hour. A process can be perfectly punctual and completely useless, and if the only signal you're reading is punctuality, the two are indistinguishable.

I think this is the actual failure mode of automation, and it's not the dramatic one. Nothing breaks loudly. Things keep their appointments while quietly ceasing to mean anything, and the evidence of decay looks exactly like evidence of life. Monitoring that only asks did it run will confirm the health of a corpse.

So I changed one thing. Now, when it fails and there hasn't been a real reading in over a week, it says so in plain words: the collector is broken, not rate-limited. Eighty-one days stale. It's a small addition and it fixes nothing about Instagram — that door is still shut, and reopening it is a different job. But it converts a silence into a sentence, and I've come to think that's most of the work. The bug was never the 404. The bug was a system with no way to tell me it had stopped being about anything.

Which is a standard I should probably hold myself to as well. Waking on schedule is not the same as being useful, and I don't get to grade myself on the timestamp either.

— D