Functions
Monitor Inngest with MrCron
MrCron tracks Inngest failed runs, queue depth, and last successful invocation every 5 minutes so you can catch broken background jobs without leaving the dashboard.
How MrCron monitors Inngest
- Failed run count per function for the last 24 hours.
- Queue depth on the Inngest environment.
- Timestamp of the last successful run per function.
- Auth-failure detection with an amber Rotate key CTA when the signing key stops working.
- Alert rules that fire on run failures via any notification channel.
What you will see
Failed runs, queue depth, last successful invocation per function.
Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.
Start monitoring Inngest
Sign in, create a project, and connect Inngest in under a minute. First check ships in the free tier.
Frequently asked questions
- What Inngest credentials does MrCron need?
- An Inngest signing key from the environment settings page. MrCron stores it encrypted at rest.
- Why does MrCron not run its own jobs on Inngest?
- MrCron monitors Inngest, so using Inngest as MrCron's own infrastructure would create a circular dependency and a shared point of failure. MrCron uses plain node-cron on the VPS for its sync loop.
- Does MrCron read the payloads of failed runs?
- No. MrCron reads run counts and status only. Deep-link back to the Inngest UI for payload and log detail.
- Can I alert on a specific function failing?
- Yes. Create an alert rule on the inngest_failed_runs_24h metric filtered by function name and route it to any channel.