Cadence vs RecurringTasks
Honest compare. RecurringTasks = spawn next page on schedule (sit-back automation). Cadence = preview 10, confirm, fill horizon.
| Cadence | RecurringTasks | |
|---|---|---|
| Model | Preview the next 10, then confirm | Spawn the next page on a schedule |
| Preview | Yes — live Next 10 before any write | No horizon preview before create |
| Who writes | You — confirm is the only write | The schedule writes for you |
| Edits | Your Notion edits always win | Product path dependent |
| Duplicates | One row per rule + date | Product path dependent |
| Free | 1 rule · $0 | 3 rules |
| Paid | Solo $9 / Team $19 | Pro $12/mo |
| Gallery | Not yet | Listed — template gallery available |
| Also ships | Confirm modal, pause rules, workspace plans | Cron, pause/resume, 3-rule free, billing live |
Why people look ahead
“they’ll appear on my calendar only at the day they’re already due which makes it very bad for planning.”
“I can go a year in the future on the calendar and nothing will be there.”
2sync: “No future task preview… they do not exist in your database until the scheduled moment arrives.”
RecurringTasks is not broken — it ships Gallery, cron, pause/resume, a 3-rule free tier, and live billing. Cadence is for people who want to see the next few weeks as real rows before anything is written. Why the calendar stays empty. If this occurrence never appeared, use the config checklist. Wider landscape: integrations that write rows.