A status code is not a side effect, and a stop button is not a stop.
Tuesday night we moved a real estate client's listings sync off their edge functions onto a small worker on Railway, about five dollars a month. Two nights later we took over image hosting too, and found an edge function that kept chaining itself for 35 minutes after we unscheduled its cron.
Unscheduled is not stopped. That became the sentence of the whole week.
Friday the podcast published episode two on its own in 107 seconds, but it cut one clip out of seven. I had fixed that exact bug last week by setting execute once to false at the node level, except that node reads its own parameter, which defaults to true. So the fix looked applied and was not. I cut the other six by hand and checked every single post submission for its actual status instead of trusting the accepted response.
Wednesday, email tracking for the same client returned ok to every event and wrote nothing. It was inserting into a column that did not exist, the database threw the error away, and the vendor dashboard showed green all day.
This is why the construction-tech workbook build this week was all guards and visibility. Refuse to approve a workbook mid extraction. Make a chained re-extraction visible to the client. Show why a re-extract was refused instead of silently failing. A stop button that does not stop is a lie the interface tells the operator.
A status code is not a side effect. The system telling you it succeeded and the system actually doing the work are two different claims. Count the thing it was supposed to produce, and go look at it.
AI Diagnostic | All insights