Ultimate

X_DB_SIBLING_SCOPE_TIMEOUT

Means

a nested transaction scope waited too long for its sibling

Typical cause

two withTransaction calls were started under one outer transaction and the first never finished inside siblingWaitMs — usually because its body awaits the second, which cannot start until the first returns

Fix

await withTransaction(first); await withTransaction(second) — one after the other, never a nested body awaiting a sibling — or raise the wait: withTransaction(fn, { siblingWaitMs: 120000 })

Listed under Entity and database

This page as markdown