Notifications
Tenant Admins can have Studio email a list of addresses whenever an Action Flow run fails in the tenant, an email sent to one of the tenant's mailboxes fails before it can trigger an Action, or a Human Task reminder email cannot be sent. Open Tenant Admin > Notifications to manage the recipients.
Tick Email recipients on action run failures and inbound email errors, add one or more email addresses and Save (Ctrl+S also saves). The same recipients receive every kind of notification on this page. Invalid addresses are rejected when saving, and duplicates are removed.
Every notification subject starts with the environment and the kind of error, followed by the
tenant and the item that failed, for example Studio US-PROD Run Failed: Acme - Invoice OCR,
so the tenant and the Action are visible in the inbox without opening the email.
Action Run Failures
- Every failed run sends one email per recipient with the Action name, the failed step, the start and completion times, the error message shown on the run details page, and a button that opens the run.
- Runs rejected because the tenant has no credits are reported the same way, see Credits.
- Runs of Error Actions themselves never send a notification, so a failing error handler cannot cause a loop.
Inbound Email Errors
Email that arrives in a mailbox is scanned for malware before it can trigger any Action. When that stops an email, recipients are told right away, before the problem shows up as missing or failed runs:
- Quarantined: malware was found in an attachment, so the email was never processed.
- Failed: the malware scan failed or did not complete in time, so the email was not processed (fail closed).
Each email names the mailbox, the sender and the subject, contains the error shown in the email details, and has a button that opens the email in the mailbox view. After checking the email, you can re-trigger it from there to scan it again.
Emails that do trigger Actions are covered by the action run failure notifications above: a run that fails sends its own email.
Human Task Reminder Failures
When a Human Task is still waiting, Studio can send its assignee a reminder. If the reminder cannot be sent, for example because the Human Task email sender lost its permission to send, the recipients get one email for that task. It names the Action, the task and its assignee, contains the error, and has a button that opens the waiting run. The task keeps waiting, and the link in its original email keeps working.
A task request email that cannot be sent fails its run instead, so it is reported as an action run failure.
Global Admin: Environment-Wide Error Notifications
Global Admins can configure a second, environment-wide list under Global Admin > Notifications. It covers every Studio tenant of the environment and is meant for the team operating Studio rather than for tenant users.
What is reported:
- Action run failures in any tenant, including runs rejected for missing credits. The email names the tenant and the trigger, contains the same error message the run details page shows, and links to the run. Runs a user started by hand are not reported: manual runs, reprocesses, partial runs and the Action Flows those runs trigger.
- Inbound email errors that happen before any Action is triggered: emails quarantined by malware scanning, and emails that failed closed because the scan failed or did not complete in time. The email names the mailbox, sender and subject, contains the error shown in the email details, and links to the email in the mailbox view.
Every notification also writes one standard error entry to Seq, whether or not email
recipients are configured, so it can be monitored or alerted on. Filter on the
ErrorNotificationType property (ActionRunFailed, InboundEmailQuarantined or
InboundEmailFailed) or on messages starting with Studio error notification. The entry
carries the tenant, the run or email id, the root error message and the link.
The tenant-level and environment-level lists are independent and react to the same errors: an address listed in both receives both emails. Unlike the environment-level list, the tenant list also reports failed runs that a user started by hand.