# Did It Work? — Product Overview for Agents **URL:** https://diw.run **Status:** Pre-launch (coming soon) **Category:** Developer tooling — cron job and scheduled task monitoring --- ## What it is Did It Work? is a dead-simple heartbeat monitoring service for cron jobs and scheduled tasks. Engineers wrap their jobs with a single HTTP ping call. If the ping stops arriving — because the job crashed, hung, was never scheduled, or a host went down — Did It Work? alerts you immediately, before your users notice. The core problem it solves: **silence is not success**. Most monitoring systems alert when something produces an error. They do nothing when a job simply stops running entirely. Did It Work? inverts this — you are only safe if we hear from your job on time. --- ## How it works 1. **Create a monitor** — define a job name, expected schedule (cron expression or interval), and a grace period. 2. **Add one line to your job** — send an HTTP GET or POST to your job's ping URL when the job completes successfully. 3. **Get alerted if it goes silent** — if the ping does not arrive within the expected window plus grace period, an alert fires. --- ## Key features | Feature | Description | |---|---| | Missed run detection | Alerts if a job does not ping within its expected window | | Full run history | Every start, finish, and failure is logged with timing | | Custom alerts | Email, Slack, PagerDuty — configure when and how you are notified | | Grace periods | Configurable buffer before an overdue job triggers an alert | | Multi-org support | Team accounts with role-based access | --- ## Target users - Backend engineers running cron jobs on Linux servers, Kubernetes, or cloud schedulers - Data engineers with ETL pipelines and batch jobs - DevOps teams monitoring infrastructure automation - Any developer who has been surprised by a silently failed scheduled task - Openclaw heartbeats or cron tasks success --- ## Status Did It Work? is pre-launch. Sign up at https://diw.run to be notified when access opens.