Skip to content

docs(tasks): document optional timezone on task create/update (chat#1881 3c) #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sweetmantech merged 2 commits into from
Jul 22, 2026
Merged

docs(tasks): document optional timezone on task create/update (chat#1881 3c) #275

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f66aeb
docs(tasks): document optional timezone on task create/update (chat#1…
sweetmantech Jul 22, 2026
6fd8e6f
docs(tasks): add structured default UTC to create timezone field (cha…
sweetmantech Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions api-reference/openapi/releases.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3058,6 +3058,12 @@
"description": "Cron expression defining when the task runs (e.g., '0 9 * * 4' for Thursdays at 9 AM)",
"example": "0 9 * * 4"
},
"timezone": {
"type": "string",
"default": "UTC",
"description": "Optional IANA time zone (e.g. America/New_York) the cron schedule is interpreted in, DST-aware. Defaults to UTC. Applied to the Trigger.dev schedule (the source of truth); not stored separately.",
"example": "America/New_York"
},
Comment on lines +3061 to +3066

@cubic-dev-ai cubic-dev-ai Bot Jul 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Missing minLength: 1 on timezone in UpdateTaskRequest. Every other updatable string field in this schema (title, prompt, schedule, model) enforces minLength: 1 to reject empty-string updates. Add it for consistency — an empty IANA timezone string would be invalid anyway.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At api-reference/openapi/releases.json, line 3061:

<comment>Missing `minLength: 1` on `timezone` in UpdateTaskRequest. Every other updatable string field in this schema (title, prompt, schedule, model) enforces `minLength: 1` to reject empty-string updates. Add it for consistency — an empty IANA timezone string would be invalid anyway.</comment>

<file context>
@@ -3058,6 +3058,11 @@
             "description": "Cron expression defining when the task runs (e.g., '0 9 * * 4' for Thursdays at 9 AM)",
             "example": "0 9 * * 4"
           },
+          "timezone": {
+            "type": "string",
+            "description": "Optional IANA time zone (e.g. America/New_York) the cron schedule is interpreted in, DST-aware. Defaults to UTC. Applied to the Trigger.dev schedule (the source of truth); not stored separately.",
</file context>
Suggested change
"timezone": {
"type": "string",
"description": "Optional IANA time zone (e.g. America/New_York) the cron schedule is interpreted in, DST-aware. Defaults to UTC. Applied to the Trigger.dev schedule (the source of truth); not stored separately.",
"example": "America/New_York"
},
"timezone": {
"type": "string",
"minLength": 1,
"description": "Optional IANA time zone the cron is interpreted in (DST-aware). If sent, updates the Trigger.dev schedule; a timezone-only change re-syncs the schedule. A cron-only update preserves the existing time zone.",
"example": "America/New_York"
}

"account_id": {
"type": "string",
"format": "uuid",
Expand Down Expand Up @@ -4114,6 +4120,11 @@
"description": "New cron expression. If sent, must be non-empty and valid for your environment.",
"example": "0 10 * * 4"
},
"timezone": {
"type": "string",
"description": "Optional IANA time zone the cron is interpreted in (DST-aware). If sent, updates the Trigger.dev schedule; a timezone-only change re-syncs the schedule. A cron-only update preserves the existing time zone.",
"example": "America/New_York"
},
"account_id": {
"type": "string",
"format": "uuid",
Expand Down