Block 1 - Test Run
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
Automatically detect when your scheduled or polling trigger workflows stop running. Unlike error handlers that catch failures when workflows execute, this catches the silent killer: workflows that ...
n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.n8n, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.stopanderror, n8n-nodes-base.noop, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Julian Kaiser.
Original n8n.io sourceAutomatically detect when your scheduled or polling-trigger workflows stop running. Unlike error handlers that catch failures when workflows execute, this catches the silent killer: workflows that simply never trigger at all — broken schedules, accidental deactivation, or trigger node bugs.
No hardcoded workflow list needed. It auto-discovers every active scheduled workflow and infers the expected run frequency from their trigger configuration.
The max age calculation adds safety margins automatically: daily workflows get 48 hours (to survive weekends), weekly gets 8 days, monthly gets 35 days, and so on.
skip-monitoring so it doesn't try to monitor itselfPROJECT_ID in the "Discover Scheduled Workflows" code node to limit monitoring to a specific n8n projectPROJECT_ID to monitor only one project, or leave empty to monitor all.skip-monitoring to opt it out.parseCronMaxAge function if you need different thresholds.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Monitor scheduled workflow health in n8n with automatic trigger checks |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | DevOps |
| Author | Julian Kaiser |
| Published | 10 Feb 2026 |
Use the JSON export at /data/workflows/13290/13290.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Automatically detect when your scheduled or polling trigger workflows stop running. Unlike error handlers that catch failures when workflows execute, this catches the silent killer: workflows that ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.