Skip to content

fix(schedule-engine): extend cron trigger retry budget across short DB outages #5128

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

Closed
umeraamir69 wants to merge 1 commit into from
Closed

fix(schedule-engine): extend cron trigger retry budget across short DB outages #5128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 6 additions & 1 deletion internal-packages/schedule-engine/src/engine/workerCatalog.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,13 @@ export const scheduleWorkerCatalog = {
lastScheduleTime: z.coerce.date().optional(),
}),
visibilityTimeoutMs: 60_000,
// Longer than a short Postgres outage (~30–60s). With the redis-worker
// defaults this budget covers roughly 9–10 minutes before DLQ, so a brief
// DB blip delays a tick instead of permanently stopping the schedule chain.
// See https://github.com/triggerdotdev/trigger.dev/issues/5120
retry: {
maxAttempts: 5,
maxAttempts: 15,
maxTimeoutInMs: 60_000,
Comment on lines +25 to +26

@devin-ai-integration devin-ai-integration Bot Nov 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔍 Missing schedule recovery release note

The longer retry budget changes customer-visible schedule recovery, but this PR adds no release note. The server-change rules require one for user-facing server fixes.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

},
},
};