Logs page

There are two levels of logging in the platform:

  • The Executions page includes a single record for every execution in the selected workspace

  • The logs page lists all the logs for all the flows in the selected workspace.

Table of Contents

Searching & filtering logs

Use the search field to find logs for a specific step in a flow.

time interval default view

Choose to filter by one or more flow names to concentrate on the logs from a specific flow or flows.

For example you may choose to examine all flows for a specific component.

  • Click the dropdown and use the check-boxes to select the relevant flows.

  • Start typing a flow name to find it in the list.

  • Click clear to deselect all flows and return to the default view showing all executions from active flows.

This filter allows you to concentrate on logs of one or more flows by selecting the check-boxes in front of their names in the drop-down menu.

flow name logs filtering
  • Click the time interval filter and use the calendar & clock popup to find executions from a specific timeframe which may span months or minutes.

  • Click apply to apply the filter.

time interval logs filtering

By default you can see logs at all levels. Use the checkboxes to choose one or more log levels from the filter to reduce the number of logs you display.

This enables you to focus on and troubleshoot errors of a specific type like error, debug etc.:

level log filtering

The log levels are as follows:


This filter includes all other log entries for which the log level is not set. These logs are usually generated by the platform root processors or included code libraries.


Outputs everything your component can show, including elements of the data passing through the component. This should be used with extreme caution and for limited periods


Designates fine-grained informational events that are most useful to debug an application.


This is the default setting and is recommended for use in production flows. Info level logs are added providing information on successful executions. No confidential data is included in these logs.


Warning level messages are logged. A warning does not indicate a flow has failed, but is indicative of a possible future issue.


The logs only include errors. An error indicates that a flow has actually failed.


Severe error that will prevent the flow execution from continuing. This error indicates a major platform problem.

Debug and trace level logs may render data passing through the component as plain text. This should be used with extreme caution and for limited periods. Always check your logging levels before moving a flow from staging to production.