Understanding Integration Hub Usage Dashboard and Transaction CountOverview This article provides clarity on the Integration Hub Usage Dashboard in ServiceNow and explains why the transaction count (or Use Count) may increase more than expected. Issue We observed that the transaction count in the Integration Hub usage dashboard is growing faster than anticipated. To investigate and monitor this growth, it's important to understand how ServiceNow tracks Integration Hub activity. Root Cause The "Use Count" field in the Integration Hub Usage [sys_hub_usage] table is automatically updated by the Integration Hub framework each time an action or spoke is executed as part of a flow or automation. How "Use Count" Works Automated Tracking👉🏻 ServiceNow automatically updates the "Use Count" each time an Integration Hub action (such as a spoke or custom action) is triggered.Incremental Increase👉🏻 Each invocation of the spoke/action adds one count to the total usage.Flows Count Too👉🏻 Not just manual invocations, but scheduled flows, subflows, and reused actions also increment the count each time they are executed.👉🏻 If a flow calls a subflow that includes multiple actions, each action is counted separately. Conclusion An unexpectedly high Integration Hub transaction count is typically due to high-frequency flows or repeated spoke invocations. Monitoring and optimizing flow designs can help manage usage and avoid hitting licensing limits. Useful References 📘 IntegrationHub Usage Also Counts Integrations Triggered by Flowhttps://www.servicenow.com/community/developer-blog/integrationhub-usage-also-counts-integrations-triggered-by-flow/ba-p/2406117