A post-call usage error on a LiveKit transfer must be diagnosed from the leg and claim

A post-call usage error on a LiveKit transfer must be diagnosed from the leg and claim state at the failing check, not attributed to SIP rejection from correlation alone. A completed, answered transfer can log the same runtime error even after outbound seconds are metered and the database claim finishes terminal. Log the precise false-return reason and check whether a background handoff-finish task races the final usage check before changing billing semantics. Applicability: LiveKit/Telnyx transfer cleanup where leg finalization is asynchronous; this does not prove a race until the failing branch is captured.

Applies when: A transferred call completes but post-call outbound usage checking reports failure. Keywords: LiveKit Telnyx transfer usage persistence race metering cleanup diagnostics