AlpacaKeep
Frühen Zugang sichern
← Alle Hilfe-Artikel
Fortgeschritten

How repeating tasks work

Why repeating tasks only appear one at a time, and how a backdated completion sets the next due date.

Dieser Artikel ist vorerst nur auf Englisch verfügbar. Wir übersetzen das Hilfe-Center - weitere Sprachen folgen in Kürze.

Repeating tasks in AlpacaKeep are "completion-first." The next task only appears when you mark the current one done. Nothing is filled in ahead of time.

What "completion-first" means

Think of it like a relay. You hold the baton until you finish, then the next runner gets it. Your Tasks list never fills up with months of future copies. You always see just the one task you are on. When you mark it done, the next one appears with its new due date.

This keeps your list short and honest. A task you have not done yet is the only one that exists.

Backdated completion: an example

The next due date counts from the day you actually finished, not from the original due date.

Say a vaccine task is due Tuesday, but you give the shot and mark it done on Saturday. If it repeats every 6 weeks, the next one is due 6 weeks from Saturday, not from Tuesday. That keeps the gap between doses correct.

Good to know. This is what you want for health jobs. The wait should start from when you did it, so the medicine timing stays right.

When repeating stops

If you set an end condition when you made the task, the chain stops on its own:

  • An end date stops it after that day.
  • End after N times stops it after that many tasks.

When the end is reached, you mark the last task done and no new task appears. If you set no end condition, the task simply keeps repeating.

  • Create a task (one-off or repeating)
  • Routines: save and reuse a task

Verwandte Artikel

Suchst du etwas anderes?

Alle Hilfe-Artikel durchsuchen →