Good day Elisson,
Thank you for your return. Based on my investigations, here is some additionnal explanation :
Generally we call this "near real-time". The system processes these notifications as fast as its able and the data will make it to the end user once all the systems along the chain have done their job. The actual timing depends on the load on the region at the time, the lag on the user's internet connection, and the speed in which the user's machine can process the notification.
Regards,
------------------------------
Mamadou DIOP
CERITEK
------------------------------
Original Message:
Sent: 12-20-2025 09:45
From: Elisson Fernandes
Subject: Genesys' calculation rules for SLA updates
Good morning!
Just to complement Stephan's response:
the calculation interval is 30 minutes, while the field itself is updated in real time, on an interaction-by-interaction basis.
For example:
The first interaction is answered within the SLA, and the indicator is updated immediately.
Shortly after, a second call is not answered within the SLA, and the indicator is updated again to reflect this new interaction.

In other words, although the SLA is calculated over a 30-minute window, the impact of each interaction is reflected in real time in the view.
------------------------------
Elisson Fernandes
------------------------------
Original Message:
Sent: 12-19-2025 10:03
From: Stephan Taljaard
Subject: Genesys' calculation rules for SLA updates
Good Day Mamadou
According to my understanding the interval is 30 minutes, unless I am not understanding the question correctly.
This also provides more information regarding the SLA calculation options - https://help.mypurecloud.com/glossary/service-level/#:~:text=Service%20level%20target%20is%20a,answered%20within%20the%20SLA%20threshold.

Found this in the community as well - https://help.mypurecloud.com/glossary/service-level/#:~:text=Service%20level%20target%20is%20a,answered%20within%20the%20SLA%20threshold.
Regards
------------------------------
Stephan Taljaard
EMBEDIT s.r.o