What problem are you trying to solve?
I’m trying to operate a multi-tenant, self-hosted n8n instance where workflow builders own their own schedules. Today, any user can create a Schedule Trigger or Cron node that fires every second (or every few seconds) — there’s no built-in guardrail an admin can set to enforce a sensible minimum interval.
This impacts self-hosted and enterprise operators because a single misconfigured schedule (e.g., “every 1 second” instead of “every 1 minute”) can:
- Saturate the executions queue and starve other workflows
- Hammer downstream APIs and trigger rate-limits / bans for the whole org
- Inflate execution storage and database growth
- Run up cloud/compute costs unexpectedly
Right now operators have no declarative way to say “no schedule on this instance may fire more often than every N seconds.”