A 403 on reschedule leaves the queue message stuck for the full 300 s claim
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cloud, typescript
- Domain
- backend, distributed-systems
Research direction
Start in the processMessage path of @vercel/queue, where the reschedule failure is logged and swallowed, and in handleCallback, which still returns HTTP 200. Then check directiveCallWithRetries, which retries only network errors and 429s, and the world-vercel retry callback tied to #1999. Done means a 403 on reschedule is either retried or falls back to the trigger's retryAfterSeconds, with the test showing the message is not left for the 300 s claim.
Written by the indexing model from the issue text.
Description
What happens
When a step's retry reschedule (changeVisibility) gets a 403 Forbidden, @vercel/queue's processMessage logs Failed to reschedule message for retry: and returns, and handleCallback still answers the push with HTTP 200. The message is then neither acknowledged nor rescheduled, so it only comes back when the push claim expires, about 305 s later.
directiveCallWithRetries retries only network errors and 429s with Retry-After, so a 403 is never retried.
Why it matters
The world-vercel retry callback asks for a 1 s retry after a failed sendMessage, but when Queues answers that sendMessage with 403, the reschedule usually gets the same 403. A step that should retry in 1 s then waits about 5 minutes. We saw 28 of these 403s in 14 days (26 on one day), on production and preview deployments, all using the deployment's OIDC token. In each case we checked, the flow was redelivered 305 s after the failed invocation.
Versions
@workflow/world-vercel5.0.1 with@vercel/queue0.5.1, and 5.2.0 with@vercel/queue0.8.0 (both bundled by eve); the retry, reschedule and swallow logic is the same in both.- Vercel Functions, iad1.
Asks
- Retry the reschedule on 403, or fall back to the trigger's
retryAfterSeconds, instead of waiting out the claim. - Is a 403 from Queues on a valid deployment OIDC token expected and transient? Happy to share request ids privately.
Related: #1999, which added the retry callback because the default was a 300 s lock.
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 401
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 201
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/workflow
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
node-module-esbuild-plugin: getImportedIdentifier only checks the first named import when locating a violationPossibly taken @div-cowboy claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel/workflow#5057 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
code-transform.mdx §ID Generation omits the package-shipped `name@version` ID formPossibly taken @Mohith26 claimed this 113 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
Similar issues
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
device-management-toolkit/sample-web-ui#3711 ·
Maintainers usually reply within 1 day
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
Closing a pinned tab jumps to the Tabs section instead of the next open pinned tabPossibly taken @seenimohamed claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ardia-browser/ardia#2769 ·
Maintainers usually reply within 1 day