Skip to main content
Version: 12 - TBD

Connection report bundle

The Connection Report Bundle enables you to keep track of the connections used by individual executions, as well as entire execution trees (i.e. processes). It counts both productive and dev mode connections. It consists of two main parts:

  • A connection count wrapper for continuously counting connections, and
  • A connection count plugin action for ad-hoc counts of connections.

The connection count wrapper​

The connection count wrapper allows you to keep track of the connections used by a process, i.e. executions that are started by each other, over longer periods of time.

To use the wrapper, go to the flow or connector that you want to count, navigate to the “wrapper” tab, select the “connection count wrapper” and confirm the wrapper. No additional configuration is necessary.

Once the connection count wrapper is added to a flow, it will

  • count the connections for executions of the flow itself as well as all its child executions and
  • create a setting called “<month year>”, e.g. “August 2025” where it will continuously log the dev mode and productive connections of this flow. If the setting already exists, it will update it.

The setting will contain a list of all flows that use the connection count wrapper with the following information:

- Counted for: <flow name>  
  Dev mode connections: 0  
  Productive connections: 15  
  Number of times counted: 6  
  Total number of connections: 15

Note that:

  • The counts are sums of all connections over the course of the entire month.
  • The counts are for connections done by the execution of the flow itself, as well as all its child executions. This means that connections are counted for the entire execution tree / process.
  • You can also add the wrapper to a connector to keep track of how many times that specific connector is used in a month.
  • There is no requirement to add the wrapper to the top-most flow of a process, you can also use it to count connections for subtrees.
  • An entry for a flow will be created in the setting when it is executed for the first time in the current month. Just adding the wrapper to the flow will do nothing, only when the flow is executed will connections be counted and the count added to the setting.
  • Connections are only counted after you add the wrapper. The wrapper doesn’t count historic executions and connections.
  • Connections are counted only while the wrapper is added to the flow. When the wrapper is removed from the flow, the setting will not be updated for that flow anymore.
  • If you rename the flow, a new entry will be created in the setting using the new flow name. Counts for the old flow name will not be updated.
  • Like all wrappers, the connection count wrapper is started before the execution of the flow itself. You will see it in the dependency visualization.
  • There is no limit to the number of times you can use the wrapper. You can also use it for several flows in the same process, which will allow you to keep track of overall connection count as well as counts for subtrees. Note that this will add slightly to the processing time of your process.
  • The connection count wrapper doesn’t use any connections.

The “count connections” button​

The connection count bundle also includes a plugin which, if activated, displays a button “count connections” in the action bar of each execution. Pressing this button will count the productive and dev mode connections for the execution and all its child executions.

Note that:

  • Counting connections should only be done after the execution as well as all its children have finished executing. Counting connections while the execution is still running is possible, but is likely to lead to an incorrect count.
  • When you press the “count connections” button, this will forward the view to an execution which does the counting. The connection count will be displayed both in the output field of that execution, as well as its status message.
  • The count connections button is independent of the connection count wrapper. Pressing the “count connections” button will not change the counts in the connection count setting for the current month. It’s an isolated operation.
  • If you have the connection count bundle installed, but don’t see the “count connections” button on executions, you need to enable the count connections plugin and plugin action. See the chapter below on how to do that.

Installing the Connection Report Bundle and enabling the “count connections” button for all executions​

To install the Connection Report Bundle, you need to have the Cloudomation default bundle repository configured in your workspace.

Navigate to the bundle manager either in the left-hand menu or via the cog symbol in the top right corner of the Cloudomation UI. Look for the bundle called “connection report” and press the “install” button in the actions column.

Once the bundle is installed, the connection count wrapper is available and can be used for any flow.

In order to use the “count connections” button to count connections for individual executions, you need to:

  • Open the connection report bundle.
  • Remove the read-only flag on the bundle by pressing the lock icon in the action bar on the top right corner of the UI. This will remove the “read only” tag on the bundle. A “changed” tag will appear to indicate that the bundle is different from the original bundle.
  • Open the “connection counter” plugin in the bundle.
  • Enable the plugin and save it.
  • Open the plugin action “count connections” for the record type “execution” in the bundle.
  • Enable the plugin action.
  • Save the plugin action.
  • Optionally, you can navigate back to the connection report bundle and set it to read-only again to avoid accidental changes to its content.

Once the plugin as well as the plugin action have been enabled, the “count connections” button will be visible on all executions.