Some work happens on a schedule — weekly reviews, monthly reports, quarterly planning. Recurring tasks regenerate themselves on the cadence you set.
Setting a recurrence
On any task, click the due-date picker, then Repeat. Choose a pattern:
- Daily — every day, every weekday, or every n days.
- Weekly — pick the days. “Monday and Thursday” is common for standup-related tasks.
- Monthly — by date (the 5th) or by weekday (the second Tuesday).
- Yearly — useful for annual reviews, contract renewals, compliance reports.
- Custom — full cron-style expression, including business-day-only patterns.
How regeneration works
Lattica creates the next occurrence when the current one is marked Done — not on the calendar trigger. This matters: if you skip a week’s standup and only mark it Done Friday, next week’s task gets created from Friday, not from the original Monday.
To override this and use strict calendar timing, enable Always regenerate from schedule in the recurrence options.
What carries over
The new occurrence inherits: title, description, assignee, priority, custom field values, attachments, and any subtasks (as fresh, uncompleted copies). What doesn’t carry over: comments, completed-state of subtasks, time logs.
Pausing and stopping
Open the task, click Recurrence → Pause to skip generation without deleting the rule. Click Stop to end the series — the current task remains, but no further occurrences are created.
Limits
To prevent runaway generation, Lattica caps a single recurrence rule at 1,000 future occurrences. If you hit that ceiling you’ve probably configured the cadence wrong — daily for ten years generates 3,650, which is fine, but every-five-minutes-forever does not.