⌘K
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?
Craiguito I’d isolate the database package before blaming Vercel or the whole template. From a clean folder, try the init with pinned tooling instead of all latest versions: corepack enable corepack prepare pnpm@9.15.4 --activate npx next-forge@latest init If it still creates the repo but fails at @repo/database, cd into the generated project and run: pnpm --filter @repo/database build That should give you the real TypeScript/ORM error instead of Turbo’s wrapper error. The log in the post only says the package build failed, not why. My guess is a version mismatch between the template’s database package and current pnpm/turbo/Node. If the package builds after pinning pnpm and Node 20, it’s a template/tooling drift issue. If it still fails, the exact error from packages/database is the part to chase.
Ryu Hi Segal, The log you posted is still Turbo’s wrapper error, not the actual database package error. I’d isolate `@repo/database` first before treating the whole template as broken. From a clean terminal, try pinning the toolchain instead of using whatever “latest” resolves to: ``` node -v corepack enable corepack prepare pnpm@9.15.4 --activate pnpm -v npx next-forge@latest init ``` If the init still fails but leaves a partial repo behind, go into that repo and run the failing package directly: ``` pnpm --filter @repo/database build ``` or: ``` cd packages/database pnpm build ``` That should show the real TypeScript / ORM / env-var error instead of only: ``` @repo/database:build exited (1) ``` I’d also check the root `package.json` after scaffolding. In a Turborepo + pnpm workspace, the `packageManager` field and lockfile matter for reproducible installs: ``` { "packageManager": "pnpm@9.15.4" } ``` Turborepo documents that field here: https://turborepo.com/docs/getting-started/add-to-existing-repository#add-a-packagemanager-field-to-root-packagejson If the package builds with Node 20 + pinned pnpm but fails with pnpm 10/latest, then this is probably template/tooling drift. If it still fails after pinning, the next useful thing to share is the first actual error from `packages/database`, not the Turbo summary.
Anshuman Bhardwaj Thanks @shige. I agree having sandbox in multiple regions will be so amazing! Passing on this feedback to our team.
Tadashi Shigeoka Thank you for the quick response, @anshumanb san! Looking forward to seeing multi-region support come to Vercel Sandbox.
Felix421 I would also like to second this request. I am with a cloud consulting firm in Germany and we would love to adopt vercel sandbox as our AI platform solution. We are as of now unfortunately unsure due to the lack of EU hosting. Do you already have distinct plans to expand sandboxes availability? Have a great day everyone! Best regards Felix
Amy Egan Hey Eric, I don't think the docs have automatic language translation. At least I'm not aware of it being a feature, and the docs aren't automatically translated for me when I switch my browser language. Do you have a browser extension or setting that might be automatically translating things for you?
Eric Burel Well my bad if it’s not on Vercel side actually! I’ve noticed that automated translation kicks in more and more in various application so the culprit might be Google Chrome actually. I can’t reproduce systematically, so I’ll try to figure what’s going on more precisely. I wonder if there are ways to prevent these automated localization from the website standpoint though (like forcing to respect the language indicated in the html tags etc. ?), they tend to lead to a terrible user experience in the end. There is this idea that LLMs did solve the problem of automated translation but we are quite far from that.
Pauline P. Narvas Thank you for your feedback, Jakub! I've shared this with the docs team.
Jakub T. Jankiewicz You may also mention Prisma, a popular interface to SQL database (not sure if you can call it ORM). There is an issue with deploying Next.js app from GitHub action if you use Prisma. The solution is in this StackOverflow answer: https://stackoverflow.com/a/79622676/387194 It only happen from GitHub action, when you use Vercel to deply, it works fine. It’s probably also a good idea to add this to docs. So people don’t get errors and then waste time searching or give up.
Pauline P. Narvas Heard. Appreciate the detail! The docs team are aware 
