What’s the correct approach to push WFM quality scores into the predictive dialer without breaking our pacing logic? The /api/v2/wfm/scheduling/quality/scores endpoint returns {"code":"invalid_param","message":"quality_metric_mapping_missing"} on Genesys Cloud 2024-11, and the outbound queue freezes because the dialer treats the quality flag as a DNC trigger while Architect flow OUT_QM_SYNC_V2 logs a 400 error on the REST action step. Pacing drops to 15% and abandonment rate holds at 2.8%, but compliance audits reject the batch when the quality webhook times out, don’t know why the pacing engine stays stuck on {"code":"invalid_param","message":"quality_metric_mapping_missing"}.