Settle Video Room Requests
What It Does
Meeting writes append room work, and the daily and hourly jobs drain it. The gateway flag defaults off. Registrant and attendance handlers exist, but the production paths that enqueue registrants or deliver attendance events are absent. A lease is temporary exclusion rather than proof that calls cannot overlap.
The Flow
Insert room work alongside the meeting change. Claim at most fifty due rows and commit the two-minute lease before calling out. Invoke the configured Integration Platform capability; an unconfigured gateway reports provider unavailable. Record the settled video outcome and remove its request.
When Something Fails
Roll back together with the meeting. No durable request after rollback. Leave unprocessed claims to expire. Room changes can lag behind meeting changes. Retain failed or unknown calls for another drain; settle provider-unavailable responses without an attempt cap. No room is created when the provider is unavailable, and failed calls stay pending. Keep the request if settlement fails, allowing the stored key to be retried. The provider may have acted before the meeting records that result.
Open Design Questions
The gateway flag defaults off. Registrant and attendance handlers exist, but the production paths that enqueue registrants or deliver attendance events are absent. A lease is temporary exclusion rather than proof that calls cannot overlap.