@zen-agentchecks…zen/fix-consumer-provisioning-race-k8wmt2 → main2 files · +32 −0updated 2mo agoWhen multiple concurrent requests hit consumer-provisioned tRPC procedures or MCP endpoints for the same org/user, they race to provision the consumer project via Apollo. The losers hit Prisma P2034 (transaction write conflict), unique constraint violations, or "Failed to create project" errors — all of which currently surface as 500 "Unable to set up your account" to the user.
Impact: 10 provisioning failures + 84 cascading auth errors + 2 "Unable to set up" user-facing errors in the last 24h (from Datadog service:composio-dashboard status:error).
Fix:
ensure-consumer-project.ts: Detect race-condition error signatures (P2034, unique constraint, failed to create project) and return null instead of throwing. The caller (tRPC consumerMiddleware) already falls through to resolveConsumerContext() which reads the record created by the winning request.resolve-bearer.ts (MCP path): After ensureConsumerProject returns null on a race, retry resolveProjectApiKey() to read the now-existing record instead of returning null and failing the request.null return from ensureConsumerProject correctly routes to DB-read fallback in both tRPC middleware and MCP bearer pathsOrigin: cron-ab141b543e91 / zen-cron-cedd6cd16f09
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard |  Ready | Preview, Comment | Mar 28, 2026 7:34am |