πŸ™ We need an error handler step for automation

As automations get more and more complex, there are more possibilities for failures along the way.

  • As of right now, there is now way to catch an error and do something
  • If things encounter an error where the automation chain fails, it simply fails.
  • There is no way for us to say, if something goes wrong... do "this".

But this behavior is actually critical for maintaining stable running systems.  We live in the real world where data is messy; despite our best efforts to get clean data all the time, invariably this will fail and something weird will come through.

  • In times like this, say we have a number (ie: 116) inside the timestamp column, we need a way to catch these and do something - because the standard things we're trying to do will fail (because 116 is not a timestamp, so timestamp stuff won't work).

Kinda like how we have a custom-timeout when using a "wait" task

MultiTech_0-1736259231528.png

If there was an "On Failure" branch at the end of the automation chain, that would allow us to define something to do in this instance (send an email, call a process, mark the record as an error record, etc.), we could catch these instances and maintain stability.

--------------------------------------------------------------------------------------------------------------------
Cheers; and as always, thanks for considering!

Status Open
10 1 177
1 Comment
IT_Innovations
Bronze 2
Bronze 2

If your validating data input would you still need the error handling? I see your point though. OnError event would be nice. A workaround is using appscript in place when feasible. For instance I run scheduled events on the Google sheets to reset columns instead of using Bots in appsheet to do it.