Ipaas metered flows and connectors with a proxy.

We have on use 2 connectors that interacts with an external platform. One of them is a cloud service and the other one is our local instance of the same product. In order to connect to the local server we use an ipaas proxy.

Some of the flows using these connectors are considered metered and others dont.

Are connector using the proxy not consired external connector? Or is there other factor involved? All the flows are triggered using TDX Web Services.

 

 

Asked by Josue Melgar on Thu 10/17/24 10:42 AM Last edited Thu 10/17/24 10:42 AM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Mark Sayers Thu 10/17/24 11:01 AM

Hello Josue,

We have a helpful KB here that describes the difference between a metered and a non-metered flow: https://solutions.teamdynamix.com/TDClient/1965/Portal/KB/ArticleDet?ID=143364

Definition of a Metered Flow

A flow is considered metered, and therefore counts against your licenses, when:

The flow is published AND one or more of the following is true: 

  • The flow involves a non-TeamDynamix connector or webhook 
    • The flow is triggered by a non-TeamDynamix webhook OR 
    • The flow utilizes a non-TeamDynamix connector 
  • The flow calls a child flow (or sub flow), AND the child flow utilizes a non-TeamDynamix connector 

Definition of an Un-Metered Flow 

A flow is considered un-metered, and therefore does not count against your licenses, when:

  • The flow is not published
  • The flow (and it’s called sub flows) DO NOT involve a non-TeamDynamix connector or webhook 
    • The flow is triggered by a TeamDynamix webhook OR  
    • The flow utilizes ONLY TeamDynamix connectors 
  • The flow is only called by another flow 
    • **Sub-flows cannot be considered metered. However, if the sub-flow uses non-TeamDynamix connectors, it will contribute to the parent flow being considered metered** 
  • The flow does not have any connectors OR triggers 
  • Published sandbox flows that manage production flows
No feedback