Fix a failing flow#

Most trouble in Data Transform comes down to one thing: failures are quiet. A block that fails does not stop the flow and does not raise a notification, so a run with broken blocks in it still finishes and still reports as completed. Most of the fix is to know where failures show up.

Nothing seems to have happened#

Check that the block connects back to the trigger. The flow skips blocks with no path from the trigger, and they produce no output and no error at all. A block that sits on the canvas and shows nothing after a run is usually a block that is not wired in.

If a block ran but the output looks stale, remember that a change to an argument does not re-run anything. Run the flow again.

A block shows an error#

The message appears in three places at once: on the block, in the inspector when you select the block, and in the execution log. It is never a notification.

The common causes are much the same across the whole catalogue. You left an argument blank, such as an empty passphrase on AES Decrypt or an empty pattern on Regex Extract / Replace. The input is not the shape the block expects, such as hex with characters outside 0-9 and a-f, or a timestamp the block cannot recognise. Or a block that reaches the network could not get there, which affects HTTP Request and DNS over HTTPS.

Fix the argument and run the flow again.

A failing block passes nothing on, so everything downstream runs with empty input. One blank argument early in a long pipeline can produce a run full of empty results with a single real cause at the top of it. Read the execution log from the top, rather than debug the last block.

The whole run failed#

A 'Flow run failed' notification, with a Retry button, means the app could not execute the flow at all rather than that a block misbehaved. The usual cause is a loop in the connections. Follow the wires and break the cycle.

The execution log has disappeared#

Close the log with its × and the app hides it until you reopen the feature. Nothing brings it back in the meantime. Close the Data Transform workspace tab and open it again.

If the log is present but empty after a run that clearly did something, check whether someone used the trash icon. A cleared log also clears every block's stored output.

A scheduled flow is not running#

Check the status line under the schedule controls. It reads 'Runs every ...' when the schedule is armed, and 'Enable to run on a schedule' when it is not.

An interval of zero or a negative number disables the schedule silently, with no error, so confirm the number is above one. Also check that the run does not take longer than the interval. A tick that arrives while the previous run is still going is dropped, and nothing reports it.

Schedules run only in the main window and only while the app is open. A flow in a popout window does not fire.

A file watch is not firing#

The status line reads 'Runs when the target changes while the app is open' once you pick a target and turn the toggle on.

If the watch fires but the content arrives empty, the file is probably over the 5 MB limit, or it was deleted, or it is not text. Set Emit to Path and read the file downstream instead.

If several files change together and you see only one, that is Content and Path, which pass on the most recent change only. Use Batch to receive all of them.

A 'File watch could not start' notification usually means the path no longer exists or the app cannot read it.

Actions you cannot undo#

There is no undo anywhere in the feature, and several actions are immediate and unconfirmed: a tab you close, a block you delete, a log you clear, and a library entry you delete, which also closes the tab that entry is open in.

Export a flow you cannot afford to lose before you do any of them.