The Quality Manager evaluation score for Agent ID AG-8842 diverges from the WFM forecasted adherence metric by approximately 15% during the 09:00-12:00 CET window. The Architect flow is configured to trigger evaluations only after successful call completion, yet the quality.evaluations endpoint returns a timestamp mismatch. Specifically, the created_date in the Quality module shows 2023-10-25T09:15:00Z, while the WFM report aggregates this event at 2023-10-25T09:45:00Z. This 30-minute lag causes the adherence calculation to incorrectly flag the agent as non-compliant during the shift start. The flow uses a Data Action node to post to the Quality API immediately upon call hang-up, confirmed by the 201 Created response in the debug logs. However, the WFM dashboard, which relies on the workforce-management:reports:view permission set, does not reflect this update until the hourly aggregation job completes. Is there a known caching layer between the Quality module and WFM report generation that introduces this delay? The environment is Genesys Cloud EU-West-1, running Architect Flow Designer v2 with the latest Quality Management integration patch. The specific report in question is the Agent Adherence Summary using the Real-Time filter. Attempts to refresh the report manually via the UI yield no change, and the GET /api/v2/wfm/schedules endpoint confirms the agent was scheduled and present. The discrepancy persists across three consecutive days, affecting performance metrics for the entire team. Please advise on how to align the Quality evaluation timestamps with WFM adherence calculations or if there is a configuration setting to force immediate propagation of quality scores to the workforce management module.