Recurring wedding tasks

Open Tasks → List for wedding tasks, or Tasks → Recurring to manage daily, weekly or monthly repeats. Choose Add recurring task to create a schedule. Each repeat creates an ordinary task on its local due date. A Monday confirmation review can be complete while next Monday’s review remains open.

Set dates and responsibility

Choose the wedding, task, assigned teammate, first date and last date. Notes, timezone and skipped dates are available under the optional settings. Daily and monthly rules use the first date as their anchor. Weekly rules repeat on the selected weekdays; interval weeks are anchored to the Monday of the first week. Monthly dates clamp to the end of shorter months: a January 31 monthly review runs on February 28 or 29, then March 31. Add excluded dates for holidays or planned time away. The next five dates are shown before saving.

Repeat periods are finite and can span up to five years. A new schedule starts today or later in its selected timezone. The worker runs every five minutes; it creates tasks due on that local calendar date, without sending messages or charging usage. Due dates are date-only values, so a daylight-saving change does not move a Monday task to Sunday.

Assign only teammates who already have private workspace access. Assignment never adds a subscription seat, grants new permissions, or exposes work to an invited vendor. Reassigning a generated task changes that occurrence only. Editing the repeat changes responsibility for later occurrences.

Pause, edit, or recover

Editing a repeat affects dates that have not yet been generated. Existing task notes, dates, completion, and assignments are retained. Pause stops future generation without deleting tasks. Resume skips dates missed while paused. Include missed dates deliberately creates missing occurrences, in batches of up to 25 per pass.

Every occurrence has a retained schedule/date identity. A retry or restarted worker cannot create it twice. Deleting a generated task does not erase that identity or resurrect the task on the next run. If a project closes, a selected teammate loses access, or the schedule’s approving operator or credential loses authority, the repeat is held. An authorized operator can review the project and teammate, then save or resume it under current authority.

Task edits and assignments require the revision you reviewed. If somebody changes a task first, reload before applying your edit. If a network response is interrupted, Check saved request checks the same saved request instead of submitting another change.

Setup and scope

Team members with full access to the business can manage these tasks. API credentials need tasks:read to read it and tasks:write to manage repeats and assignments. Shared wedding access alone grants neither permission. The /api/v1/task-schedules interface uses the same services and supports separate task and recurring-schedule cursors.

Recurring generation needs the additive task-schedule migration and the recurring-project-tasks durable job, both activated in the coordinated setup phase. Until the worker is activated, the app retains your schedule but future tasks will not appear automatically. Review current worker and schedule status in Operations if a due task has not appeared. Native and existing project task views see generated tasks through their regular task interfaces.