Flow: Run the scheduler every minute so minute schedules, delays and retries fire on time
Zapier polls every 15 minutes on Free and every 2 minutes on paid plans, and n8n schedules run to the minute (https://zapier.com/pricing). Our editor offers interval schedules in minutes (minimum 5) and Delay in seconds or minutes, but on cloud the Flow queue only drains in the hourly /api/cron/tick ('17 * * * *' in vercel.json); the copy itself admits runs can start up to an hour late (messages/en/flow.json scheduleGranularity and delayGranularity). Node retries schedule jobs 15 s to 1 h out and also wait for the next tick. This silently breaks the most common small-team automation, 'every 15 minutes check X', and any follow-up delay. First scope: call processFlowQueue from the existing 5-minute /api/cron/robots route (or add a 1-minute cron for Flow only), then remove the granularity warnings. Priority: high. Effort: S. Compared with Zapier / n8n.
Comentarios 0
Sin comentarios todavía.
Ingresá para comentar