Prerequisites
- SMTP must be configured for your team (On-premises only)
- Workflow failure notifications must be enabled at the team level
- Recipients must be members of the workflow’s project
Access Requirements
| Action | Required Access |
|---|---|
| Enable or disable notifications for the team | Teams Administrator |
| Configure additional recipients for a workflow | Access to the workflow + project membership |
Setup
Step 1 — Enable Notifications for the Team
A Teams Administrator must enable workflow failure notifications before any emails are sent.
Once enabled, workflow owners automatically receive email notifications when their workflows fail — no additional setup required.
Step 2 — Configure Additional Recipients (Optional)
Workflow owners can add more recipients for individual workflows.Failure Notification Modal
The modal that opens from Failure Notifications includes:| Component | Description |
|---|---|
| Notify Workflow Owner toggle | Enable or disable notifications for the workflow owner |
| Owner email | Displays the workflow owner’s email address |
| Additional recipients dropdown | Multi-select dropdown for adding more recipients |
| Warning banner | Appears when team-level notifications are disabled |
Recipient Rules
- Only project members can be selected as recipients
- The workflow owner is automatically excluded from the dropdown to avoid duplicate notifications
- Multiple recipients can be selected simultaneously
- Recipient lists are scoped to the current team
If a warning banner appears in the modal, team-level notifications are disabled. A Teams Administrator must enable them from My Account → Settings → Enable Email Notification before any notifications will be sent.
How Notifications Work
When a workflow execution fails:- The system detects the failure
- Recipients are resolved — the workflow owner plus any additional configured recipients
- Email notifications are sent to all resolved recipients
Best Practices
- Enable notifications only for actively monitored teams
- Add only relevant stakeholders as recipients — too many recipients leads to alert fatigue
- Review recipient lists periodically, especially after team membership changes
- Verify that your organization’s spam filters do not block notification emails
- Ensure SMTP configuration remains valid
Troubleshooting
A user doesn't appear in the recipient dropdown
A user doesn't appear in the recipient dropdown
The user is not a member of the workflow’s project. Add them to the project and retry.
Warning banner appears in the modal
Warning banner appears in the modal
No email received after a failure
No email received after a failure
Check the following:
- SMTP is configured and active
- Team-level notifications are enabled
- The recipient’s email address is valid
- Application logs show no email delivery errors
- Organization spam filters are not blocking notification emails