When a message becomes “poisoned” (fails repeatedly and can’t be processed), there’s no way to manually remove it. Attempting to query or lease the message via API returns a 404 Message Not Found error, leaving developers with no option but to wait for the message TTL to expire (up to 7 days, or 24 …

Update: it’s on the roadmap to make moving poisoned messages to the latest deployment possible For now, you can manually move messages to a different topic that is not pinned to the deployment if they reach some number of retries. Hope that helps in the meantime!

Hey @wiktorwisniewski94-4 , welcome to the community! Thank you for sharing this, I’ll pass it onto the team.

Hello @mayven , thank you for the reply! Can you share how it’s done? I didn’t know you can move messages :sweat_smile:

Add ability to manually delete/purge poisoned messages in Vercel Queues

Feedback

Topic		Replies	Views
Vercel Queues sendMessage returns 404 DEPLOYMENT_NOT_FOUND during local development Help cli , queues	6	36	April 24, 2026
Message reset keeps getting pushed further to the future v0 v0	3	45	July 20, 2025
Any ETA for Message Queue? Discussions queues	15	221	March 2, 2026
Vercel Queues: consumer callback never invoked on Next.js 16 (monorepo) Help	4	22	April 24, 2026
Vercel Queues hidden message size limit issues Help analytics , usage , docs , queues	4	35	April 22, 2026

Add ability to manually delete/purge poisoned messages in Vercel Queues

Related topics