Running Flow Usage Reports For Your Workspace

Created by Brian Glick, Modified on Wed, 5 Nov at 5:09 AM by Brian Glick

In this article:

Overview

Within the Chain.io Portal, customers are able to run reports that give them insights into their Integration and Flow Usage. This information includes total number of Flows executed, number of Failed Flows, Skipped Flows, and Successful Flows, within a custom date range. Reports can only be downloaded by the portal user who requested the report generation.

How To Run A Flow Usage Report

To run a Flow Usage Report, login to your Workspace at https://portal.chain.io/ 

On the right hand side of the navigation bar you will see the menu icon, click the icon.



In the menu that appears, select Reports.

workspace-landing-highlight.png

 

On the next screen, you will see some configuration options for your Flow Usage Report.

flow-usage-reports-landing.png

Begin by selecting the Integrations you would like your report to contain. You can select individual Integrations or multiple. The checkbox at the top allows you to select all integrations in your Workspace.

 

select-integrations.png

Next, select the Start Date of your report.

select-start-date.png

And then select the End Date for your report.

select-end-date.png

Finally, click the Generate Report button to begin the process of gathering the data and compiling your report.

generate-report.png

Downloading Your Generated Report

Once your report has been generated a link labeled Download will appear at the end of the row allowing you to download the report as a CSV.

 

download.png

Click the Download link to initiate the download of your report. Once your report has been downloaded, you can open it in your preferred CSV reader.

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article