#queues

Amy Egan Nice idea! Thanks for sharing the repo

Selçuk Çukur Thanks for sharing the repo

Vasigorc @paul-murray Hi Paul, could you please kindly take a look at this PR? I believe that I have followed Vercel Template Marketplace rules for submission. I haven’t had a follow-up from the Vercel team yet.

Paul Murray Hi @vasigorc — I don’t have time to review this today, but I’ve added it to my list.

Vasigorc Hello Paul, sorry, is this PR still on your radar?

Pauline P. Narvas Where is it in the docs? Can you share a link?

Ward Van Laer “In push mode, you can set a maximum concurrency per consumer group. This limits how many messages can be in-flight simultaneously for that group. If the limit is reached, Vercel holds back delivery until an in-flight message is acknowledged or its lease expires.“ https://vercel.com/docs/queues/concepts

Vicent Galiana We are encountering this limitation in a production-like workload using `@vercel/queue` 0.5.0 and a JavaScript `queue/v2beta` push consumer. One publish operation created 110 messages. Vercel started all 110 first-delivery callback invocations within 18.354 seconds. The consumer calls a rate-limited downstream GraphQL service, and 49 deliveries failed with HTTP 429 and required retries. We need to configure the push consumer group with a maximum concurrency of `1`. The documentation states: > “In push mode, you can set a maximum concurrency per consumer group.” However, we cannot find a supported configuration surface: * The consumer group under **Project → Observability → Queues** is read-only. * The documented `queue/v2beta` trigger schema exposes `topic`, `retryAfterSeconds`, and `initialDelaySeconds`, but no `maxConcurrency`. * `@vercel/queue` does not expose a push consumer-group update method. * `Vqs-Max-Concurrency` appears to apply only to poll-mode receive requests. Could you please confirm: 1. Is push-mode maximum concurrency currently available? 2. If it is internally configurable, can Vercel set our consumer group limit to `1`? 3. Is there a planned supported configuration through `vercel.json`, the dashboard, or an API?

Ryu I don’t think there’s a SvelteKit-specific Queues guide yet, but the important pieces should still map to SvelteKit server routes. For push mode, I’d start with the smallest setup: ``` // src/routes/api/orders/+server.ts import { json } from '@sveltejs/kit'; import { send } from '@vercel/queue'; export async function POST({ request }) { const body = await request.json(); const { messageId } = await send('orders', body); return json({ messageId }); } ``` ``` // src/routes/api/queues/process-order/+server.ts import { handleCallback } from '@vercel/queue'; export const POST = handleCallback(async (message, metadata) => { console.log('processing queue message', metadata.messageId, message); }); ``` Then make sure the trigger in `vercel.json` points at the actual SvelteKit route file, not the Next.js example path: ``` { "functions": { "src/routes/api/queues/process-order/+server.ts": { "experimentalTriggers": [ { "type": "queue/v2beta", "topic": "orders" } ] } } } ``` A common gotcha is copying the docs’ `app/api/.../route.ts` path into a SvelteKit project. That path is for Next.js, so Vercel will not attach the trigger to your SvelteKit consumer. I’d also confirm these before debugging deeper: ``` pnpm i @vercel/queue @sveltejs/adapter-vercel vercel link vercel env pull vercel dev ``` If the build still fails on Vercel, the most useful detail to share would be the first actual build error line plus your `vercel.json` and the consumer route path, with any secrets removed.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Monday I'm also seeing these transient issues using a PollingQueueClient. Occurred on May 6th, coinciding with the Workflows partial outage, and again now. Not working now: Working earlier:

Pauline P. Narvas Thanks for your feedback, Kevin! I've passed this onto our product team.