A lot of automation tools retry failed steps quietly in the background and only surface a problem once it’s persisted for days. We used to build things that way too, on an earlier internal version of what became TGArchiveTech — and it cost us a week of missing CRM records before anyone noticed.
So the current design does the opposite: any failed hop is written to the run log immediately, with the actual error returned by the destination, and — if you’ve turned on alerting — a notification goes out right away. Retries still happen automatically, but they don’t hide the fact that something needs attention.
It’s a small design choice, but it’s the one thing customers mention most often when asked why they switched from a chain of Zapier steps.