LICMCUIntegrationHubPool | Integration Hub Transactionsdetails.kb-section{margin:0 0 16px;}details.kb-section>summary{cursor:pointer;list-style:none;}details.kb-section>summary::-webkit-details-marker{display:none;}details.kb-section>summary>h2{display:inline-block;margin:0;}details.kb-section>summary::before{content:"\25B8";color:#032D42;font-weight:700;margin-right:8px;}details.kb-section[open]>summary::before{content:"\25BE";}details.kb-section h3{font-size:1em;font-weight:600;margin:12px 0 4px;} Table of Contents OverviewReproducibility Understanding the LICMCUIntegrationHubPool DefinitionHow Integration Hub Transactions Are CountedAttribution LogicIntegration Hub Usage DashboardCalculation LogicDatabase TablesRelease Dependencies Frequently Asked QuestionsTroubleshootingRelated Resources 1. Overview The licensing meter for Integration Hub transactions is the cumulative count of Integration Hub Pool transactions in the last 12 months. An Integration Hub Transaction is defined as any outbound call originating from Integration Hub, FlowDesigner, Remote Tables and/or Orchestration. What is measured: Cumulative count of Integration Hub Pool transactions in the last 12 months (SUM of monthly LICIHMIntegrationHubPool counts) Measurement level: Account/subscription-level Time period: Rolling 12 months; LICIHMIntegrationHubPool runs monthly; LICMCUIntegrationHubPool sums the last 12 monthly results Products using this definition: Integration Hub (all tiers)Automation EngineIntegration Hub / Automation Engine Transaction Add-on SKUsBU products that include Integration Hub spokes Key characteristic: Only transactions attributed to the "Integration Hub Pool" subscription ID count against the customer's allotment. Transactions marked Unlicensed, Unknown, Platform Transaction, or Product BU Transaction are not counted. 2. Reproducibility Understanding the LICMCUIntegrationHubPool Definition The Capacity Definition ID field on the Integration Hub Pool subscription specifies the usageanalytics_count_cfg record that calculates the allocated count. To look up the LICMCUIntegrationHubPool definition: Navigate to the usageanalytics_count_cfg tableFilter by: definition_id = LICMCUIntegrationHubPoolOpen the record and review the Script field The script aggregates results from LICIHMIntegrationHubPool. To look up that definition: Navigate to the usageanalytics_count_cfg tableFilter by: definition_id = LICIHMIntegrationHubPoolOpen the record How Integration Hub Transactions Are Counted Every outbound request executed by an IH feature is added to ua_ih_usage. Usage attribution jobs assign each transaction to a subscription: Platform Transaction — not countedProduct BU Transaction — not countedIntegration Hub Pool Transaction — counted against the allotmentUnlicensed Transaction — not countedUnknown Transaction — not counted Attribution Logic Attribution Logic v1 (up to and including Vancouver): If the transaction matches the platform transactions list, mark as Platform TransactionIf calling source is DATA_SOURCE, mark as Platform TransactionCheck metadata to determine the correct poolIf generated by a remote_table, mark as IH Pool Transaction (if IH SKU present)If spoke ID is global or custom, mark as IH Pool Transaction (if IH SKU present)If no match, mark as Unlicensed Attribution Logic v2 (Vancouver onward) - Before Yokohama: If transaction matches platform transactions list, mark as Platform TransactionIf calling source is DATA_SOURCE, mark as Platform TransactionIf no IH Pool license present, mark as UnlicensedIf Spoke ID is in the exclusion list, mark as Platform TransactionOtherwise mark as IH Pool Transaction Attribution Logic v2 - Yokohama onward: If transaction matches platform transactions list, mark as Platform TransactionIf calling source is DATA_SOURCE, mark as Platform TransactionIf Spoke ID is in the exclusion list, mark as Platform TransactionOtherwise mark as IH Pool Transaction Note: From Utah onward, both Open and Closed instances follow the attribution logic above. See KB1175817 for details. Integration Hub Usage Dashboard Customers with an IH subscription can view usage in the Subscription Overview dashboard and the Integration Hub Usage Dashboard (available from Tokyo onward via Store; default from Utah onward). The dashboard shows Unlicensed, Embedded, Platform, and Licensed transactions. Navigate to ua_ih_usage directly to view Unknown transactions. Calculation Logic LICIHMIntegrationHubPool (runs monthly): Adds previous month IH usages from ua_ih_usage where Subscription ID = IntegrationHubPool, plus previous month Orchestration executions from orch_execution. LICMCUIntegrationHubPool (sums last 12 months): var lastYear = SNC.UsageAnalyticsScriptUtils.getLast12MonthAccrualTimeStamp(); var gr = new GlideAggregate('usageanalytics_count'); gr.addQuery('definition_id', 'LICIHMIntegrationHubPool'); gr.addQuery('time_stamp', 'IN', lastYear); gr.addAggregate('SUM', 'count'); gr.groupBy('definition_id'); gr.query(); var total = 0; if (gr.next()) { total = gr.getAggregate('SUM', 'count'); } answer = total; Database Tables usageanalytics_count_cfg - stores LICMCUIntegrationHubPool and LICIHMIntegrationHubPool definitionsusageanalytics_count - stores monthly count resultsua_ih_usage - Integration Hub Usage table; one record per outbound callua_ih_feature_usage - Integration Hub Feature Usage tableorch_execution - Orchestration execution records Release Dependencies Integration Hub Usage Dashboard: Tokyo or later. See KB1175817 for details on attribution logic changes in the Utah release. 3. Frequently Asked Questions 1. We are using Integration Hub spokes but Subscription Management shows 0 usage. Why? Common causes: Unlicensed: no active subscription matched. Verify the customer has a valid IH license. If valid, raise a support case.Unknown: the instance state was Open at attribution time. Navigate to ua_instance_state and verify ServiceNow State and Vendor State are both Closed. 2. Can old transactions attributed as Unknown be corrected? Yes. ServiceNow Support can re-run attribution logic for past months. See KB1125070. 3. What is the difference between Unlicensed and Unknown transactions? Unlicensed: no active subscription matched. Unknown: instance state was Open at attribution time or licensing metadata was incomplete. 4. Are Integration Hub spokes included in BU products counted? Transactions from BU-included spokes are attributed as Product BU Transaction and are not counted. See KB1224540. 5. What happens if we exceed our contracted transaction allotment? There is no option to reduce historical usage retroactively. Contact your ServiceNow representative to acquire an IH or Automation Engine subscription or Transaction Add-on SKU. 4. Troubleshooting Issue: Usage shows 0 or unexpected number in Subscription Management Common causes: ua_ih_usage records marked Unknown (instance was Open) or Unlicensed (no matching subscription). Resolution: Check ua_instance_state — verify ServiceNow State and Vendor State are both Closed.Review the IH Usage Dashboard for Unlicensed transactions.If Unknown transactions exist from when the instance was Open, contact Support to request re-attribution via KB1125070. Issue: Usage count appears higher than expected Common causes: Orchestration executions included in the monthly count; remote table transactions attributed as IH Pool. Resolution: Use the IH Usage Dashboard to break down transactions by type and spoke. Navigate to ua_ih_usage directly to filter by subscription = IntegrationHubPool. 5. Related Resources Related Knowledge Base Articles KB1175817 - Changes to Integration Hub license attribution in Utah releaseKB1125070 - How to request Integration Hub transaction re-attributionKB1224540 - Integration Hub spokes included in BU products Product Documentation Integration Hub Spokes Entitlements: servicenow.comServiceNow Product Documentation: docs.servicenow.com Need additional help? If your question isn't answered in this KB, click the thumbs down button and provide feedback, or open a Now Support Case to request assistance.