Computed Hours in AEP License usage is always same from May 27, may I know what's the reason | Community
Skip to main content
Level 2
June 22, 2026
Question

Computed Hours in AEP License usage is always same from May 27, may I know what's the reason

  • June 22, 2026
  • 1 reply
  • 38 views

Computed Hours in AEP License usage is always same from May 27, may I know what's the reason

 

 

1 reply

Level 2
June 23, 2026

@Mia-jm_Wa  Computed Hours represent the usage of Data Distiller service specifically, the amount of time the query engine spends reading, processing and writing data during batch query execution.

If you are seeing no change in computed hours, this is usually expected behavior and can be attributed to one or more of the following factors:

1. The License Usage Dashboard in AEP is not updated in real-time. It may relies on daily snapshot and updates only reflect once the system processes the next snapshot cycle.
2. If you are using scheduled queries using Data Distiller jobs, they might be processing the same dataset repeatedly with no change in size or complexity.
Also in few cases, they may have failed silently or stopped running. In both scenarios, computed hours may not increase meaningfully.
3. Computed hours only increase when query workloads are executed, if you/your team haven't run new data processing jobs then it’s expected that usage remains unchanged.

Are you checking on production or development sandboxes? And your queries are automated or ad-hoc? Did you able to check if your datasets are actually changing in size?

You can refer below for Monitoring Query service usage 
URL : https://experienceleague.adobe.com/en/docs/experience-platform/query/data-distiller/license-usage
&
For license usage dashboard
URL : https://experienceleague.adobe.com/en/docs/experience-platform/dashboards/guides/license-usage

This unchanged computed hours is possibly an indication of stable workloads or no recent query activity.
 

Mia-jm_WaAuthor
Level 2
July 1, 2026

Hi ​@kalarav.vasavada  the problem is that we have daily queries running, but computed hours was not updating after May