Quick question about the screen recording integration with our WFM schedule data. We are seeing a 2-3 minute lag when agents initiate recordings during shift handovers in the Chicago timezone. The Architect flow triggers correctly, but the metadata timestamp mismatches the actual schedule start time. Is this a known latency issue with the recording service API, or should I adjust the flow execution order to ensure the schedule context is fully committed before the recording starts?
The root of the issue is that the recording service caches schedule data asynchronously, causing the timestamp mismatch. When building AppFoundry integrations, this latency is common during high-concurrency periods like shift changes. Implement a retry loop with exponential backoff in your flow to wait for the metadata to sync before proceeding.