Queue callback error: Error [MessageNotFoundError]: Message id not found
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 365
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 169
Description
On Vercel World I have a workflow that failed a bunch of times because of a 429 from a service I use.
I tried replaying them to get a successful completion, and I managed that. But then I saw a bunch of 500 responses for this request POST /.well-known/workflow/v1/flow saying:
Queue callback error: Error [MessageNotFoundError]: Message 019b0002-a03e-75d8-95f2-a947a3fd9eb4 not found
at async u (.next/server/chunks/10997_next_dist_esm_build_templates_app-route_419f0528.js:14268:3136)
at async s (.next/server/chunks/10997_next_dist_esm_build_templates_app-route_419f0528.js:14268:4174)
at async S (.next/server/chunks/10997_next_dist_esm_build_templates_app-route_419f0528.js:14268:5241)
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the POST /.well-known/workflow/v1/flow request and the reported Queue callback error, then trace the MessageNotFoundError through the generated stack references if the source mapping is available. Reproduce the replay-after-429 scenario and determine why the callback returns 500 for a missing message; the issue does not specify an expected behavior beyond avoiding these failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100