Why Didn't My Workflow Notification Go Out?

Last updated: November 13, 2026

When a Workflow doesn't go out, the cause is usually one of its settings rather than an error in Ambition.

This article explains how to track down why a Workflow didn't send.

Required permissions:

The Workflows: Edit permission is required to check and fix a Workflow's settings.

Make Sure the Workflow Is Active

Head to Hub --> Workflows. By default, this list only includes active Workflows.
Can't find it? Open the Filters drawer with the filter button and change the active filter to Inactive.
If the Workflow shows up there, select Edit from the actions menu in its row.
Turn the Active Status toggle back to Active and save with Update Workflow.

Select the Workflow's name to open its overview page.
Look at the jobs list, where each job's Status reads Pending, Success, or Failed.
No jobs means the Workflow's conditions haven't been met yet. For a Failed job, check the common causes below.

Metric Based Alerts send once per period: An alert will only be sent once per person for each Time Group, and won't be sent for values reached before the Workflow was created.
Ambition can't post to the channel:
- Ambition must be invited to private or invite-only Slack channels.
- Microsoft Teams users must install the Ambition app to receive direct messages.
- Webex direct messages will fail if the email address on the person's Ambition account doesn't match their Webex account.
Recipients are limited by Level of Access: Report Workflows set to Restricted will only email the Workflow's creator.
The Leaderboard was empty or too long: Empty Leaderboards aren't sent unless Always send notifications is set to Yes, and Leaderboards sent to Slack will fail if Number of results is set above 50.
The recipient unsubscribed: People who unsubscribed from a Workflow type will no longer receive its emails.