MinorStaffing and reliabilityApril 24, 2026

Booking claim workflow reliability

Booking claim synchronization now avoids interactive transaction pressure during background claim creation, reducing timeout risk after admin booking changes and payment confirmations.

All studios

What changed

Booking claim synchronization now keeps its database transaction smaller and moves the heavier email-preparation lookup outside the transaction.

Background claim creation no longer depends on starting an interactive Prisma transaction, so open freelancer claim rounds can still be created when transaction slots are temporarily constrained.

Runtime incident reporting is also more defensive when a server error does not include a usable request URL.

What changed

Why this matters

Studios using staff claim workflows should see fewer timeout-related claim sync failures after booking changes.
Production monitoring now keeps reporting the original Prisma/runtime issue instead of failing on missing request context.