Repository navigation
fix(schedule-engine): extend cron trigger retry budget across short DB outages - #5128
umeraamir69 wants to merge 1 commit into
Conversation
…B outages A ~30s Postgres outage exhausted the old 5-attempt budget and dead-lettered schedule.triggerScheduledTask jobs, permanently breaking the next-tick chain.
|
|
Hi @umeraamir69, thanks for your interest in contributing! This project requires that pull request authors are vouched, and you are not in the list of vouched users. This PR will be closed automatically. See https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md for more details. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| maxAttempts: 15, | ||
| maxTimeoutInMs: 60_000, |
There was a problem hiding this comment.
🔍 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.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Summary
schedule.triggerScheduledTaskfrommaxAttempts: 5to15withmaxTimeoutInMs: 60_000so a brief Postgres outage delays a tick instead of dead-lettering the chain permanentlyTest plan