CQD and Reporting Latency

%3CLINGO-SUB%20id%3D%22lingo-sub-2669951%22%20slang%3D%22en-US%22%3ECQD%20and%20Reporting%20Latency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2669951%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20looking%20at%20Auto-Attendant%20and%20Call%20Quality%20Analytics%20provided%20here%20for%20TEAMS%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Faa-cq-cqd-historical-reports%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Faa-cq-cqd-historical-reports%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20thing%20that%20jumped%20out%20at%20me%20that%20I%20wanted%20to%20understand%20better%20-%20the%20below%20section%20indicates%20that%20data%20is%20not%20committed%20to%20the%20pipeline%20for%20up%20to%2030%20minutes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20this%20mean%20if%20I%20were%20using%20this%20report%20I%20could%20not%20see%20actual%20%22real-time%22%20calls%20in%20the%20Auto-Attendant%20in%20queue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20in%20previous%20versions%20of%20Teams%2C%20the%20information%20on%20calls%20did%20not%20commit%20to%20the%20database%20until%20the%20caller%20had%20hung%20up%2C%20at%20which%20point%20the%20call%20record%20was%20then%20added%20to%20the%20database.%26nbsp%3B%20Is%20this%20the%20same%20with%20the%20current%20incarnation%20of%20Teams%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EData%20latency%20and%20AA%20%26amp%3B%20CQ%20analytics%3C%2FP%3E%3CP%3EData%20will%20be%20available%20in%20the%20CQD%20data%20pipeline%20within%2030%20minutes.%3C%2FP%3E%3CP%3EYou%20will%20have%20to%20refresh%20the%20data%20to%20see%20the%20new%20analytics%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2669951%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2670105%22%20slang%3D%22en-US%22%3ERe%3A%20CQD%20and%20Reporting%20Latency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2670105%22%20slang%3D%22en-US%22%3EUnfortunately%20if%20I%20recall%20correctly%20none%20of%20this%20is%20real%20time.%20Due%20to%20the%20sheer%20number%20of%20users%20using%20Teams%20I%20can%20fully%20imagine%20Microsoft%20can%E2%80%99t%20commit%20to%20real%20time%20data%20when%20it%20comes%20to%20call%20quality%20data%20and%20there%20will%20always%20be%20delays.%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

I'm looking at Auto-Attendant and Call Quality Analytics provided here for TEAMS - https://docs.microsoft.com/en-us/microsoftteams/aa-cq-cqd-historical-reports

 

One thing that jumped out at me that I wanted to understand better - the below section indicates that data is not committed to the pipeline for up to 30 minutes.

 

Does this mean if I were using this report I could not see actual "real-time" calls in the Auto-Attendant in queue?

 

Also, in previous versions of Teams, the information on calls did not commit to the database until the caller had hung up, at which point the call record was then added to the database.  Is this the same with the current incarnation of Teams?

 

Data latency and AA & CQ analytics

Data will be available in the CQD data pipeline within 30 minutes.

You will have to refresh the data to see the new analytics data.

 

Thank you.

2 Replies
Unfortunately if I recall correctly none of this is real time. Due to the sheer number of users using Teams I can fully imagine Microsoft can’t commit to real time data when it comes to call quality data and there will always be delays.
Okay this is what I thought, so it's fair to say that this data is always 30 minutes behind in what is being shown in these reports?

These are all historical.