This article covers:
When a failure notification email is sent, and when it is not
Who receives it
What the email includes
In short
When an automation fails, either a platform failure or a destination push failure, StellarAlgo emails the automation's creator and the org's assigned CS/AM lead with what happened, what to do, and a link to the automation. A run that simply matches 0 fans is not a failure and does not send an email.
When you'll get an email
A platform failure or a destination push failure on an automation triggers a notification.
One email is sent per failed run, even if the same run failed on more than one destination.
Note: A run that completes but matches 0 fans is not treated as a failure and does not trigger a notification.
Who receives it
The creator of the automation
The StellarAlgo CSM for the account
.
What's in the email
A subject line naming the automation and the failure context
A link to the automation
The trigger name and date
What happened, in plain language
What to do about it
A link to the relevant help article for that failure type
FAQ
I didn't get an email for a failed run. Why not?
Check whether you're the automation's creator or the org's assigned CS/AM lead, only those two roles receive it. If neither is set up correctly for your org, no one gets the email. Contact support to confirm and to review the failed run itself.
Does a 0-fans run send an email?
No. That is not treated as a failure.
Can I turn these emails off?
Not yet. There is no per-user opt-out in this version.
What if the same automation fails on two different destinations at once?
You get one email, not one per destination.
Still need help?
For what each failure type means and how to resolve it, see Troubleshooting automation runs. Contact StellarAlgo support and include the automation name and roughly when the failure occurred.