Recurring tasks
Work that comes back on a schedule — how the timing works, and the two edge cases that trip people up.
Some work returns: a weekly report, a monthly access review, a quarterly retrospective. Set a recurrence on a task and Krrim creates the next one for you.
Setting one up
Open a task, go to Recurrence, and choose a pattern:
- Daily, optionally on weekdays only
- Weekly, on chosen days
- Monthly, on a day of the month
- Yearly
Then decide when it stops: never, on a date, or after a number of occurrences.
Each occurrence is a new task with its own key, its own assignee and its own history. Completing one does not affect the next, and editing one does not retroactively edit the ones already created.
Times are local, always
A recurrence set for 09:00 fires at 09:00 in your workspace's timezone — in January and in July.
This sounds obvious and is the thing schedulers most often get wrong. Storing the time in UTC and converting gives you a task that arrives at 09:00 in winter and 08:00 in summer, which people report as "it drifts".
Set your workspace timezone in Settings → General before you rely on this.
Month-end clamps rather than skips
A monthly series on the 31st fires on the last day of shorter months — 28 or 29 February, 30 April — not never.
The naive reading of "the 31st" produces no February occurrence at all, so a monthly series would quietly fire seven times a year. Clamping is what people mean by "month end".
No duplicates, ever
Occurrences are recorded so the same one cannot be created twice, even if the scheduler runs twice or retries after a failure. A duplicate notification is an annoyance; a duplicate task is something a person has to clean up by hand, so this one is enforced strictly rather than checked hopefully.
Ending a series
Turning off recurrence stops future occurrences. Tasks already created stay — they are real work with real history, and deleting them because the schedule changed would take that history with them.
If you set the series to end "after N occurrences", Krrim counts the ones actually created rather than re-deriving the schedule, so pausing and resuming does not lose your place.