Copy Attachment unknown REST usage in IntegrationHub usage table

[George Chen]

Hi folks

There have been some interesting discussions on how each Integration Hub usage gets counted, however, in the instances I am working on including PDI, I cannot replicate the usage count on Copy/Attachment Flow Action.  Below screenshot excerpt is a simple concept to clone attachments on incident records created and automatically put them through to a new problem record.  This test, however, does not seem to trigger the Usage Count which is shown in the screenshot at bottom. 

In the organisation I am working for there have been surprisingly large usage on each month's Integration Hub; some of which I can replicate, e.g. var r = new sn_ws.RESTMessageV2('Name of the REST message record ', 'PUT_ByReference'), but for Copy/Attachment Flow Action, this one seems a mystery and I wonder if anyone has more insights?  

https://developer.servicenow.com/dev.do#!/reference/api/washingtondc/server/c_RESTMessageV2API

Your response would be appreciated.

Reference SNOW Community post:

https://www.servicenow.com/community/now-platform-forum/how-does-servicenow-count-integration-hub-tr...

[Max D_ding]

Hi George,

We have had the same issue yesterday for one of our Customers.

We were able to identify the root cause which is related to snap (Antivirus Scanning) of attachments.

Once the Flow copies the attachment it will be send to snap and this will result in an outbound rest call.

Since Integrationhub is defined as: "An Integration Hub Transaction is defined as any outbound call originating from Integration Hub, FlowDesigner, Remote Tables and/or Orchestration, and any external document indexed via External Content Connectors. This includes any operation, action, orchestration from Integration Hub, Remote Tables or Orchestration resulting in an outbound call." and we have an outbound call (to snap) this is counted.

I believe that this might be an issue on ServiceNow side as this is probably unexpected behaviour. We were able to identify that even if the attachment already was virus scanned, when copied it will be send again to virus scanning.

Best regards,

Max