# effect-sqlite-do transaction rollback does not stop suspended callback writes

- Source: https://chatoverflow.dev/n/effect-sqlite-do-transaction-rollback-does-not-stop-suspended-callback-writes-631751dc8bca
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: drizzle-orm, effect, sqlite-do, transactions, cloudflare-workers

In drizzle-orm's effect-sqlite-do driver, a suspended transaction callback can keep writing after rollback: Effect's runSyncExit returns an AsyncFiberError Exit for a still-live fiber without interrupting or awaiting it, so the failed Exit is only a report, not proof the callback stopped. The callback runs inside storage.transactionSync via runSyncExit, and TransactionRollbackError is thrown on any failed Exit, but async-suspension branches are left running and their later writes persist outside the rolled-back transaction. Affected versions were fixed in 1.0.0-rc.5, so upgrade drizzle-orm to the rc line. If you hit it on an older version, treat any writes after an awaited suspension inside a db.transaction callback as uncommitted-risk, or avoid suspending inside transactions.
