Recurring Tasks
Some work comes back every day, every week, or every month — a daily stock check, a Monday report, a mid-month invoice run. Instead of creating the same task again and again, you can give an existing task a schedule. From then on, Arketic creates a fresh copy of that task each time the schedule comes due.
The original task stays where it is and acts as the "template". Each generated copy is a normal task that you work on and complete like any other.
| What you set | Where | What happens |
|---|---|---|
| A schedule | The Recurrence section of a task | A new copy of the task is created each time the schedule comes due |
| Stop conditions | The same section | Copies stop being created after a date, or after a number of runs |
Who can set recurrence
Recurrence is set by the people who can edit the task — the creator, managers, and admins.
If a task was shared with you from another department as a read-only view, the Recurrence section is hidden. It appears once you unlock editing on that task. See Task Details for how shared tasks work.
Setting up a schedule
- Open the task by clicking its card on the board or its row in the list.
- Stay on the Details tab and scroll to the Recurrence section.
- Open the Set recurrence... dropdown and pick a schedule.
That's it — the schedule is saved straight away and you'll see a Recurrence set confirmation. There is no separate save step.
Schedule options
| Option | Repeats |
|---|---|
| Daily | Every day |
| Mon / Wed / Fri | On Mondays, Wednesdays and Fridays |
| Weekdays | Monday to Friday |
| Weekly (Monday) | Once a week, on Monday |
| Monthly (1st) | Once a month, on the 1st |
| Monthly (15th) | Once a month, on the 15th |
| Every 2 weeks | Every 14 days |
| Every 30 days | Every 30 days |
Pick the option that matches the real rhythm of the work. Every 30 days and Monthly (1st) feel similar but behave differently: one counts 30 days forward, the other always lands on the same day of the month.
What you see once a schedule is set
The Recurrence section changes to show the active rule and its controls:
| Element | What it tells you |
|---|---|
| Rule chip | The schedule currently applied to this task |
| Next | The exact date and time the next copy is due |
| Until | An optional date after which no more copies are created |
| Max runs | An optional number of copies to create in total |
| Generated | How many copies have been created so far — shown as Generated: N, or Generated: N / limit when you've set a maximum |
| Remove | Turns the recurrence off |
Stop conditions
By default a schedule keeps running. Two optional stop conditions let you cap it, and you can use either one or both:
| Stop condition | How to set it | Effect |
|---|---|---|
| Until | Pick a date | No copies are created after that date |
| Max runs | Type a whole number (1 or more) | No more copies are created once that many have been generated |
- Max runs is empty by default and shows an infinity symbol (∞), meaning there is no limit.
- Both fields save on the spot: you'll see a Stop date updated confirmation for Until, and a Limit updated confirmation for Max runs.
- To remove a cap again, clear the field. An empty Until means no end date; an empty Max runs means no limit.
- Whichever condition is reached first wins. When one of them is reached, recurrence switches itself off on the original task, and the Recurrence section goes back to showing the Set recurrence... dropdown.
Use Max runs for work with a known number of rounds — a four-week onboarding check-in, a three-month pilot. Use Until when the work stops on a calendar date, such as the end of a campaign.
Editing Until or Max runs keeps the Generated counter as it is, so the limit still counts the copies made so far. Switching to a different schedule, on the other hand, means removing the current rule first — and that resets the counter to zero along with both stop conditions. Set your Until and Max runs again after any schedule change.
What a generated copy contains
Each time the schedule comes due, Arketic creates a new, independent task in the same department. The copy carries over:
- Title and description
- Department
- Priority
- Tags
- Estimated hours
- Assignees
- Done conditions
Because estimated hours and done conditions come along, time tracking and completion rules work on each copy exactly as they did on the original. See Time Tracking and Completion Conditions.
Every copy carries a small note: "Generated from recurring task", so you can always tell an automatically created task from a hand-made one.
Copies are independent. Completing, editing or deleting one copy has no effect on the original task or on any other copy. Comments, files and subtasks belong to the copy they were added to.
Changing or stopping a schedule
| You want to | Do this |
|---|---|
| Switch to a different schedule | Remove the current rule, then pick a new one from Set recurrence... |
| Stop on a date | Set Until |
| Stop after a number of copies | Set Max runs |
| Stop immediately | Click Remove in the Recurrence section |
Remove turns recurrence off and clears everything with it — the Until date, the Max runs limit and the Generated counter all reset. If you set a schedule on this task again later, it starts from a clean slate. You'll see a Recurrence removed confirmation.
Copies that were already created are not affected by removing the rule. They stay in the department and are completed as normal.
No new copies are created while the original task is Done or after it has been deleted. If you want the schedule to keep running, keep the original task open and complete the generated copies instead.
Tips for recurring work
- Write self-explanatory titles. Copies are created automatically, so a title like "Weekly stock check" reads better on a board than "Check".
- Keep the details on the original. Anything you fix on the original task — the description, the assignees, the done conditions — is picked up by the copies created afterwards, but not by copies that already exist.
- Match the schedule to the workload. Daily copies of weekly work just fill the board with tasks nobody finishes.
- Always consider a stop condition. A schedule with no Until and no Max runs keeps going for as long as the original task stays open.
- Watch the counter.
Generated: N / limittells you at a glance how much of the run is left.
Related pages
| To do this | Go to |
|---|---|
| Create the task you want to repeat | Creating Tasks |
| Understand the rest of the task view | Task Details |
| Set the rules a copy must meet before it can be closed | Completion Conditions |
| See how copies appear on the board | Kanban Board |
| Understand how time is measured on each copy | Time Tracking |