Just noticed that Scheduled Adherence reports in Genesys Cloud are showing significant gaps for agents utilizing our 15 BYOC trunks in the AP-Southeast-1 region. While the WEM dashboard indicates these agents are ‘On Schedule’ and ‘Available,’ the detailed adherence view flags them as non-compliant during specific 15-minute intervals. This occurs despite the SIP trunks maintaining stable registration and zero drop rates during those windows. The issue seems isolated to outbound campaign agents rather than inbound queue members. We are running the latest WEM version with standard Architect flows for campaign status updates. The discrepancy appears when the agent transitions from ‘After Call Work’ back to ‘Ready’ status. Is there a known latency issue with status propagation from the BYOC trunk side to the WEM engine in this region? We need to ensure our compliance reporting accurately reflects agent availability to avoid false penalties for the team.