last comment
⌘K
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.“ 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 conf
