Viewing logs


Having accessed run logs and selected the view logs option for a given flow run, you can view:

Insights summary

The insights summary is divided into three functional areas:

In the top, right-hand corner (1) you'll find additional options via an ellipses menu - these options will vary, depending on whether the run succeeded or failed. See Additional options for more information.

In the top panel (2), you can see basic details for the process flow (name, id, version and status, and how triggered) together with duration, CPU usage time, data used, and score.

The lower panel (3) shows every step (i.e. every shape) in the flow in processing sequence, with the following information:



The name given for the shape in the process flow. If your process flow includes custom names for shapes, these are shown here - otherwise the default name is displayed.

Flow id

Triggered by

How the process run was triggered - e.g. a manual run, a scheduled run, etc.

Flow version

The flow version. You'll see this number in the canvas title block (immediately below the title) when editing the flow.


The underlying microservice for the shape.


Date & time that the run started.

CPU time

The total amount of time spent processing.


Total time take for the run to complete (includes any setup time as well as processing time).

Payload count

The total number of payloads processed.

Payload size

The total size of processed payloads.


A visual representation of where each step starts and finishes.


This is a measure of how efficient/expensive (in terms of processing) your process flows are, based on the volume of data processed per second - 999 is the highest score.

Your score is based on all runs for all process flows associated with your company profile. This includes flows that are:

  • Triggered by a schedule, webhook, or event

  • Initialised by an API request

  • Run manually

  • Enabled or disabled when run

  • Draft or deployed status when run

Understanding scores

Process flow scores are based on the volume of data processed per second - 999 is the highest score.

If your score is on the low side, it may be that your process flow is necessarily complex - including items such as scripts, transformations, flow control, caches, etc., has an impact on your score.

However, it's always worth checking a low scored process flow further as there may be places where your process flows can be optimised (for example, does a flow include lots of mapping transformations that could be achieved in a single script?). A quick scan down the shapes list in the lower panel will show, at a glance, which shapes in your flow are taking longer to process or perhaps processing unusually high volumes of data.

If your score is on the low side and you're satisfied that the process flow is built optimally, don't worry too much about the score - it's just there as an indicator.

See our Best practice for building process flows section for advice on building efficient process flows.

Detailed logs

In the lower panel of the insights summary, you can click any entry to access detailed logs:

In the top section, you can see a full history of what happened during this step - this will often display over multiple pages:

In the lower section, you can view and download any payloads associated with this step. Click the 'view' icon associated with any payload to see the contents:

...the payload is displayed:

Longer payloads are trimmed but you can use the download option to retrieve the full content:

Payloads are available for 72 hours after the process flow has run.

Additional options

The ellipses icon in the top, right-hand corner provides access to additional options. These options vary, depending on whether the run failed or succeeded:

If a run is successful, you have the option to download run logs. If the run failed, you can download logs and also retry the run.

Last updated