Compare two runs

See what changed in the data between two reads, what differs between two calls, and what changed in the script's definition.

Something worked before and does not now, or a step changed a value you did not expect. The panel can put two states side by side: two reads of the data, two calls, or two versions of the script's definition.

Compare the data before and after a step

Open the Data tab and tick Track changes. A Changes bar appears under the toolbar. Changed values stay marked until you press Clear marks. See Changes.
Click through the script, for example press Next on the page.
Press Previous change and Next change to walk the marked values, or open the Changes view for a list with the time and the step of each. See Changes view.
Press Compare data. Pick a Before and an After read from the last 12, each labelled with its time and step. Since this step began picks the first read of the current step and the latest. You can also load a JSON file as a read. See Compare data.

The two reads open Side by side: Before on the left, After on the right, the rows lined up. A changed value is amber, an added key green with a hatched gap on the other side, a removed one red. Unchanged keys fold to one grey line. Previous and Next (or the arrow keys) walk the differences. Rows of a list are lined up by Id or name first, so deleting one row reads as one gap. List shows the differences as a list instead. See Side by side.

Compare two calls

Open the Calls tab and select a call.
Press Compare with previous (or d) to diff it against the earlier call to the same place. A failed call also gets Compare with last success (or Shift+D). The buttons appear only when the same place was called before.
To compare any two calls, press b on the first to make it the baseline, then select the other. A Compare tab sets the input, options and output of the two calls side by side, and its first line says how the baseline was chosen; a part with no difference says so on one line. See Compare.
When both calls are debug runs of one kind, the comparison starts with their steps: the status and time before and after, the difference, and a totals row. A step that ran in one and was skipped in the other is tagged. Under it, two Integration Procedure runs compare their Original input and Response side by side. See Debug tab.

The Changes tab of a call sets the data before and after it side by side too. To compare any two JSON texts, such as two responses from a log, press Compare JSON… in the Tools row of Settings, paste them into Before and After, and press Compare. See Compare JSON.

Compare the definition

Before you change the script in the Designer, open Structure, turn on Advanced and choose Export, then Definition JSON. Keep the file. See Export.
After the change, press Compare definition… and pick that file. It may also be a debug bundle that holds the definition.
The elements are listed as Added, Removed, Renamed or Changed, with a note of what changed: label, required, show rule, validation, remote target, options, Set Values and help text. Click a name to select it. See Compare definition.

Comparisons honour Mask values: with it on, the values are placeholders and only the shape of the change is shown. To share what you found, see Report a problem.