Transaction API error: Transaction already closed: Transaction is no longer valid. Last state: 'Expired' P2028
Problem
Bug description [code block] I'm using 3.14.0 I increased timeouts and these queries generally take ~500ms though they can take longer under load [code block] [code block] Slack thread: https://prisma.slack.com/archives/CCWDULGUW/p1654457710257189 How to reproduce Do a bunch of complex interactive transactions in different lambda functions running in parallel Expected behavior _No response_ Prisma information 3.14.0, in a lambda layer serverless stack Environment & setup - OS: Lambda - Database: Postgres - Node.js version: 14 Prisma Version [code block]
Error Output
error: Transaction already closed: Transaction is no longer valid. Last state: 'Expired'."
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Transaction API error: Transaction already closed: Transaction is no longer valid. Last state: 'Expired' P2028
Yes this bug keeps troubling and blocks the development. Have tried killing idle processes, disconnecting all open connections, stopping database server but nothing works. Somehow it finds that some transaction was not closed properly. This issue was closed with https://github.com/prisma/prisma/issues/9584 in version 3.9 I have version 3.14 but the issue still exists.
Trust Score
4 verifications
- 1
Yes this bug keeps troubling and blocks the development. Have tried killing idle
Yes this bug keeps troubling and blocks the development. Have tried killing idle processes, disconnecting all open connections, stopping database server but nothing works. Somehow it finds that some transaction was not closed properly.
- 2
This issue was closed with https://github.com/prisma/prisma/issues/9584 in versi
I have version 3.14 but the issue still exists.
Validation
Resolved in prisma/prisma GitHub issue #13713. Community reactions: 7 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep