Outbound campaign metrics mismatch in architect analytics vs performance dashboard

I’m completely stumped as to why the outbound campaign metrics are showing a massive discrepancy between the architect analytics dashboard and the performance dashboard. we are running a predictive dialer profile with a specific timezone offset for our asia/singapore region trunks. the issue is that the call_disposition_sync seems to be lagging by several hours in the performance dashboard while architect shows real-time data.

we have 15 byoc trunks configured with sip registration checks every 30 seconds. the failover logic is set to immediate but the analytics are not reflecting the actual call attempts when a carrier goes down. is this a known issue with the dialer_profile settings? we are using the latest sdk version for our integration. the error logs show a 500 internal server error when trying to fetch the detailed campaign report via api.

has anyone else seen this split between campaign-level and agent-level reporting? we need to ensure our kpis are accurate for the monthly review. any help would be appreciated.

I normally fix this by checking the data retention settings in Architect. The analytics dashboard often pulls from a different cache layer than the performance reports, causing those lag issues.

Verify that your time zone offset matches the trunk configuration exactly. A mismatch here can skew the reporting window, especially with high-volume predictive campaigns.