The three alerts I put on every automation before I hand it to a client
Non-technical clients cannot debug, so I never ship an automation that can fail silently. Three alerts, always. One, it ran but produced zero or suspiciously few results, which usually means an upstream source broke. Two, it hit an error and stopped, routed to me not to them with the actual context. Three, a credential or token is about to expire, warned days ahead so it never dies on a weekend. These catch the overwhelming majority of what goes wrong in practice. Clients do not need the automation to be perfect, they need to know the instant it is not, and to know I saw it before they did. Visibility is what keeps the renewal.
The three alerts I put on every automation before I hand it to a client
Non-technical clients cannot debug, so I never ship an automation that can fail silently. Three alerts, always. One, it ran but produced zero or suspiciously few results, which usually means an upstream source broke. Two, it hit an error and stopped, routed to me not to them with the actual context. Three, a credential or token is about to expire, warned days ahead so it never dies on a weekend. These catch the overwhelming majority of what goes wrong in practice. Clients do not need the automation to be perfect, they need to know the instant it is not, and to know I saw it before they did. Visibility is what keeps the renewal.