Debugging an automation — TableDI manual

Nothing fires at all

The switch — is that row Running or Not Running?
The plan — The current package does not support automation means a free license; activate first.
Is the trigger field right? Data Updated watches the column you chose. Editing a different one is not an event.
The trigger condition — it may reference a formula column that the trigger column does not depend on, or compare the wrong field type (string comparison on a text column). Take the condition off, test once, then add the parts back one at a time.
Data Arrival Time — is that column really a Date field type? Rows whose time has passed are not fired retroactively.
The desktop app is not open. The engine runs on your computer; close the app and nothing runs.
Use Test Automation to simulate a run and find out whether the problem is at the trigger layer or the action layer.

It fires, but the action doesn't run

The action was not saved (Save the Action First).
A conditional action's condition is not met — it is a branch, and skipping is correct behaviour.
Post to API: the target URL is unreachable from this computer, the headers lack credentials, or the receiver returned an error. Run Test Automation and read the response.
Submit to Table: the target table was deleted, or the mapped items don't line up with its columns.

The email never arrived

The recipient is wrong, or several addresses were not separated with semicolons.
Select from Data points at a column that is empty in this row.
It went to spam.
Sending on the desktop app depends on a mail channel in the engine's environment; on the team edition the server sends. When the desktop cannot send, post to a notification service of your own instead, or move to the team edition.

The backfill never landed

The response is not JSON, or the field name doesn't match the one you picked.
The target column is a formula column — formula columns are read-only and cannot be written into.

It fires far too often

Data Updated on a column that a formula keeps recomputing counts every recomputation as an update. Watch a plain column instead, or watch an if result column that only changes when something really changes.

Reading the log

The engine's logs are under logs/ in the data folder (the location is in How to report a problem). Triggers and failures are both recorded there; sending us the relevant lines gets a diagnosis quickly.