Skip to content
Docs menu

Recurring issues in Venom Tasks

Make an issue on a schedule in Venom Tasks, daily, weekly on chosen days, monthly or every few weeks, in your time zone, with pause, resume, an end date and an option to skip while the last one is open.

View .md

Some work comes back on a schedule: the weekly dependency bump, the monthly invoice check, the on-call handover. A recurring issue makes that issue for you, once per occurrence, in the team that owns it.

Set one up

Open the team's settings (/tasks/settings/teams/<KEY>) and go to Recurring issues. The section lists the team's series with their schedule, the next occurrence and the last issue made. New recurring issue asks for:

  • the issue: a title, a description (markdown), a priority, an assignee and labels (the team's and the workspace's);
  • the schedule (below);
  • Skip while the last one is open: no new issue while the one the series made last is not done or canceled.

The form shows the next three occurrences as you edit. Each row has Edit, Pause (or Resume) and Delete. Anyone who can create issues can manage recurring issues.

Schedules

Repeat When
Daily every day
Weekly on the days you pick, every week
Monthly on a day of the month. Days 29, 30 and 31 fall on the last day of a shorter month (the 31st is 30 April and 28 February)
Every few weeks every 2 to 52 weeks, on the start date's weekday, counted from the start date

Every schedule has a time of day, a time zone, a start date and an optional end date. The time is wall-clock time in that zone, so a 09:00 issue stays at 09:00 when the clocks change. A time that does not exist on the day the clocks go forward (02:30 in New York in March) runs when the clock reaches it after the jump (03:30). A time that happens twice when they go back runs the first time.

How issues are made

The cloud's cron checks every minute. Each occurrence makes exactly one issue, even when two cron runs overlap: the series and the day are recorded together, and a second attempt finds the record and stops. The issue takes the team's default state, and Venom Tasks is its creator. A label that was archived, or an assignee who left the org, is left off rather than failing the issue.

If the cron could not run for a while, the series makes one issue for the latest occurrence that fell due and moves on. It does not make a backlog of issues for the days it missed. A paused series makes nothing. On resume it waits for the next occurrence from that moment. Changing the schedule does the same. Past the end date the row shows Ended.

With Skip while the last one is open, an occurrence that falls due while the previous issue is still open is recorded as skipped and makes no issue.

On the issue

An issue a series made shows Recurring and its occurrence date in the properties pane, with an Edit series link back to the series in the team's settings. Deleting a series keeps the issues it made. They just lose the link.

API

The same as the app, over /tasks/api (see the Tasks API):

Method and path What
GET, POST /tasks/api/teams/{id}/recurring list a team's series; create one
GET, PATCH, DELETE /tasks/api/recurring/{id} read; change (any field, plus paused); delete

A series is {title, description, labelIds, assigneeId, priority, schedule, skipIfOpen}. schedule is:

{
  "repeat": "weekly",
  "days": [1, 3],
  "time": "09:00",
  "timezone": "Europe/Berlin",
  "startDate": "2026-11-09",
  "endDate": null
}

repeat is daily, weekly (with days, 0 = Sunday to 6 = Saturday), monthly (with dayOfMonth, 1 to 31) or weeks (with everyWeeks, 2 to 52). Responses add paused, nextOn and nextAt (the next occurrence's day and instant, null when paused or ended), lastOn and lastIssue. A bad schedule is a 400 whose param names the field, like schedule.days. A team keeps up to 100 series.