The amount of time an agent had the work item open, calculated by CloseDateTime – AcceptedDateTime. Handle time stops when the agent closes the work item or the after conversation work time ends, whichever happens first.
The amount of time an agent is actively working on a work item in their console. Active time is tracked only for tasks routed using the tab-based capacity model. It's tracked only when the work tab is open and in focus in the service console. If the agent switches console tabs, the time spent on the other tabs isn't counted. Active time continues to count if you switch to a new browser tab or window. Active time stops when the agent closes the work item or the after conversation work time ends, whichever happens first.
However, there can be some scenarios where the Active Time of the agent displays 0 after working on Omni-Channel work items.
The case is created manually.
The created/assigned time and accept time is less than 1 second.
The chat is disconnected before the work record saves.
The Omni-Channel setting for Status-Based Capacity Model is enabled in an org.
"Currently, there is no direct fix for Active Time displaying 0 in all scenarios. The following steps can help diagnose the root cause:"
Step 1: Confirm Routing Model — "Verify that the org is using the tab-based capacity model, as Active Time is only tracked under this model. Navigate to Setup > Omni-Channel Settings and confirm the capacity model in use."
Step 2: Check Work Item Creation Method — "If cases or work items are being created manually (not via Omni-Channel routing), Active Time will display 0. Ensure work items are routed through Omni-Channel."
Step 3: Review Status-Based Capacity — "If the org has Status-Based Capacity Model enabled, Active Time tracking is not supported. This is a known limitation."
Developer Doc: AgentWork
000382097

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.