Analyzing an execution

An execution page will include all information about a certain execution.

While the execution is still running, the page will update in real time to reflect the states that are currently being executed:

You will notice that every state that has executed now has a "RESULT" button. Clicking on this button will reveal the output of the state, it's status (whether it succeeded or not), and its continuation decision (whether the execution should continue from it, or not).

For example. here is the result of an HTTP Request state:

Every execution might have more than 1 execution route, depending on your flow configuration. You can learn more about what routes are here.

Scrolling down on the execution page, you will see a dropdown that allows you to select which route you would like to view. As state outputs will differ between routes, you must choose a route to see the detailed outputs table below.

Execution Page Details

You will also notice that the bottom of the page has the following sections:

Entry Payload - a JSON view of the entry payload that was used to start this execution

Outputs - a JSON object containing ALL the outputs for ALL the states under the current execution

Logs - a logs stream that includes execution logs, i.e when did a certain state start and when did it finish. The logs should also include any execution errors.

Analysing condition states

Condition states are special in a sense that they have an embedded view of the condition group result.

If you click on the Condition state configuration, the condition configuration modal will open, and highlight which equations and which condition groups succeeded, and which didn't:

Condition Group Execution View