Tagged: scheduling
2026-10-17From one loop to nineteen: we measured Cloudflare Queues before running our checks on itOur probe checked servers one at a time. We measured how queue consumers ramp up, fitted a model, tested its predictions, then went to 19 messages a round.2026-10-15The round the platform cancelled and ran again, and 52 minutes of HTTP 503 on /statusA cancelled probe round leaves a job that never finishes, and /status reported it as stuck for 52 minutes. What counts as stuck now, and what we kept.2026-10-10A bug that only appeared in parallel: four servers checked twice, a fraction of a second apartOur first parallel probe rounds checked four servers twice, 0.11 to 0.24 seconds apart. Why one loop never hit it, why we rolled back, and the fix.2026-09-30Five hours when our probe ran nothing, and nothing told usOn 2026-09-23 the scheduler that starts our probe every five minutes stopped calling it. An unrelated deploy brought it back five hours later, and we only noticed nearly four hours after that, reading hourly counts. What happened, what we can and cannot say about why, and the two signals we added.2026-09-24The probe round that was cancelled at 67 secondsThree probe rounds died halfway through, and the servers left behind were not re-checked for half an hour. The cancellation was the platform doing something ordinary. The half hour was our own guard. How the window went from 30 minutes to 15, and why not to 10.2026-09-23Why we probe unclaimed servers every 12 hoursMCP Checkup checks unclaimed servers twice a day, claimed servers on the Free plan every 8 hours, and Indie servers every 15 minutes. The reasoning behind each number, what the cadence does and does not tell you, and what money does and does not change.