fix(tables): disable dispatcher task retries - #6963
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryMedium Risk Overview Retries were treated as unsafe because the loop is not fully idempotent; the comment no longer claims a crash will resume from the DB cursor via a new attempt. The config test that pinned Reviewed by Cursor Bugbot for commit f950ff1. Bugbot is set up for automated code reviews on this repo. Configure here. |
Greptile SummaryThe PR moves the table-run dispatcher directly onto the
Confidence Score: 5/5The PR appears safe to merge with no actionable correctness or security issues identified. The new machine preset is already supported and used elsewhere in the repository, while retry removal is an explicit design choice for non-idempotent dispatch work with stale-dispatch cleanup retained as the failure backstop.
|
| Filename | Overview |
|---|---|
| apps/sim/background/table-run-dispatcher.ts | Runs dispatches on medium-1x and removes retries, relying on persisted window progress and stale-dispatch cleanup for failed attempts. |
| apps/sim/background/table-run-dispatcher.test.ts | Updates the task configuration assertion for the new medium-1x preset and removes obsolete retry assertions. |
Reviews (1): Last reviewed commit: "fix(tables): run dispatcher on medium ma..." | Re-trigger Greptile
562a29c to
f950ff1
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f950ff1. Configure here.

Summary
small-2xType of Change
Testing
bun run lintChecklist