A created member's activation welcome waits for the commit, so a swallowed 40001 can no longer turn the create into a silent rollback

Shipped: October 5, 2026 at 1:37 AM UTC
Author: Kamo
Commit: a8966fd

POST **************** answered 200 with a member id and a user id that never existed (KamoCollab CP00 Task 0, 2026-10-05, sp00verify). The activation welcome ran inside MemberCreationService.create's REQUIRES_NEW transaction; its lazy read of the org's domains hit YugabyteDB 40001, the notifier swallowed it by design, the database had aborted the transaction, and the commit came back as a ROLLBACK nobody saw. It now runs through AfterCommit, like the verification and WELCOME letters beside it.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free Forever View Pricing