Automations debugging

When an automation fails, I get an email that it has failed, but no information about why. It is likely a one off situation but sometimes this adds up and the reason to the error is a mystery. It would be great to have some sort of debugging information to diagnose the problem.

For scripts, the full error would be nice, but for other actions, even getting just the basic error message that we see when testing within AT would be helpful.

We address this issue by building automation script that fails gracefully enough to provide insight in the causes of such failures. In Javascript, try->catch is ideal for writing an Airtable log of unanticipated events.

1 Like

Great idea when using scripts. I’ll have to try that out.