Nested Create Queries Succeed but Data Missing
Hello,
We’ve been encountering a critical issue when our SQL Server is under moderate load. Specifically, we’ve observed that some nested create queries executed via Prisma return a success response, but the corresponding records are later missing from the database.
This issue appears to have started after we migrated our major create workflows to Prisma (we’re currently using Prisma Client v5.0.0). Based on our investigation, it seems possible that Prisma may be returning a success response before the underlying transaction is fully committed—and in certain rollback cases, it doesn't surface an error to the application.
We came across this fix on your GitHub repo: https://github.com/prisma/prisma/pull/26166, which appears to address a similar concern related to interactive transactions.
Could you please confirm:
1. Does this issue also affect nested create operations (outside of interactive transactions)?
2. Would upgrading to the latest Prisma version resolve this behavior in nested create queries as well?
This is a critical issue for our system, and we’d appreciate your guidance on how to proceed.
We’ve been encountering a critical issue when our SQL Server is under moderate load. Specifically, we’ve observed that some nested create queries executed via Prisma return a success response, but the corresponding records are later missing from the database.
This issue appears to have started after we migrated our major create workflows to Prisma (we’re currently using Prisma Client v5.0.0). Based on our investigation, it seems possible that Prisma may be returning a success response before the underlying transaction is fully committed—and in certain rollback cases, it doesn't surface an error to the application.
We came across this fix on your GitHub repo: https://github.com/prisma/prisma/pull/26166, which appears to address a similar concern related to interactive transactions.
Could you please confirm:
1. Does this issue also affect nested create operations (outside of interactive transactions)?
2. Would upgrading to the latest Prisma version resolve this behavior in nested create queries as well?
This is a critical issue for our system, and we’d appreciate your guidance on how to proceed.
