Table of contents


Debugging can be quite frustrating in our coding journey, and it's not common for low-code editors to include an easy way to check this kind of issue.

To make it even nicer to implement server-side logics and third party integrations, Arengu includes a debugging mode to allow you to find, even faster, the error you are looking for.

Complete history of flow executions

Check every execution of each of your flows on the 'Executions' tab. The list will show you, at a glance, which executions have been completed or failed. You can refresh this list without reloading the entire page, by clicking on the 'Refresh' button.

Click on the edit button of the flow that you want to check, and go to 'Executions' tab.

Check any input and output data

Click on 'View details' to open debugging mode to check data structure, input and output data from each flow action, including third party integrations, like Twilio, SendGrid, MailJet... and any service with an API, in the editor itself.

Click on each action to see input/output data and errors in the editor.

This means that you don't need to go to your third party integration account to get execution data and check what's going on, and the editor allows you to also choose between 2 code display options: folded or raw code, as you can see in the pictures.

Choose between 2 code display options to check executions data.

Mask sensitive information

Arengu allows you to choose which data to store and show in the editor, with a checkbox. Just click on the 'Transient' option on each field to avoid its storage, in the form's edition view. It wouldn't be stored in Arengu, and it will be replaced by asterisks in debugging mode.

Activate 'Transient' checkbox on sensitive data fields to mask its data.

Before long, Arengu will also mask your credentials data from custom integrations, like API Keys and Secret Keys, and not just from form fields, to make flow edition even more secure.

Change context to another execution

The list of flow executions is also accessible from the actions edition view. For example, if you need to get data from a failed execution to set error messages from a 'If/then condition' action, you can get data from other executions from the field's drill down.

Inside drill down, click on 'Do you want to access another execution?' to access the list.

This way, you can get variables directly from other executions, even faster, and get data from other executions to configure complex conditional logics, saving a lot of time!

View of input and output data from an old execution on field drill down.