Functions
Monitor Trigger.dev with MrCron
MrCron tracks Trigger.dev run volume, failed runs, and currently executing runs every 5 minutes so you can watch background job health next to your errors and deploys.
How MrCron monitors Trigger.dev
- Runs count for the last 24 hours across your Trigger.dev project.
- Failed run count for the last 24 hours.
- Currently executing run count at the last sync.
- Auth-failure detection with an amber Rotate key CTA when the API key stops working.
- Alert rules that fire on failed-run spikes via any notification channel.
What you will see
Runs (24h), failed runs, currently executing runs.
Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.
Start monitoring Trigger.dev
Sign in, create a project, and connect Trigger.dev in under a minute. First check ships in the free tier.
Frequently asked questions
- What Trigger.dev credentials does MrCron need?
- A Trigger.dev personal API key or a project-scoped token. MrCron stores it encrypted at rest.
- Does MrCron read run payloads?
- No. MrCron reads run counts and status only. Deep-link back to the Trigger.dev UI for payload and log detail.
- Does MrCron work with self-hosted Trigger.dev?
- Yes. Point the integration at your self-hosted Trigger.dev host URL when you connect it.
- Can I alert on stuck runs?
- You can alert on the trigger_dev_executing_runs metric staying above a threshold for a sustained period. Route it to any notification channel.