MTMike Tickstemintickstem.hashnode.dev·2d ago · 6 min readCronitor Alternative: Cron Scheduling and Monitoring in One ToolCronitor is solid at what it does — it watches cron jobs you already have running somewhere and alerts you when they fail, run too long, or stop checking in. What it doesn't do is run the job for you.00
MTMike Tickstemintickstem.hashnode.dev·Jun 3 · 5 min readVercel cron alternative: what to use when built-in cron isn't enoughVercel's built-in cron triggers your serverless functions on a schedule. For simple use cases it works. But it has no failure alerts, no execution history on the Hobby plan, and no way to know whether00
MTMike Tickstemintickstem.hashnode.dev·May 26 · 4 min readHeartbeat monitoring for AI agent pipelinesYou deploy an AI agent to run nightly. It summarises data, writes a report, sends a Slack message. You set up uptime monitoring on the endpoint. The monitor stays green. Three days later you notice th10
MTMike Tickstemintickstem.hashnode.dev·May 26 · 4 min readMonitoring AI agents in productionTraditional monitoring asks one question: is the server up? If the endpoint returns 200, everything is fine. AI agents break that assumption. The server can be perfectly healthy while the agent silent00
MTMike Tickstemintickstem.hashnode.dev·May 26 · 6 min readScheduling recurring tasks in AI agent workflowsWhen you build an AI agent that does something useful — summarises documents, monitors a feed, sends a report, syncs data — you eventually hit the same question: how do I make it run on a schedule? No00