Skip to main content

Get Email Alerts When an Automation Fails

Turn on emails that tell you when an automation at your company fails, and act on the failed run.

This is currently a limited feature. Please contact your Fountain representative for more information.

Automation failure alerts are emails Fountain sends you when an automation at your company fails. Turn them on in your profile, and you hear about a failed run without watching your automation logs.

Before You Start

You need permission to manage automations and to view automation logs. Without both, the setting does not appear in your profile. Ask your Fountain admin to check your role.


Turn On Automation Failure Alerts

Alerts are off by default, and each person chooses for themselves. Turning them on for you does not turn them on for anyone else.

  1. Open the account menu at the bottom of the left sidebar and select Profile.

  2. Go to Notifications and, in the Platform section, turn on Automation failures.

  3. Select Save.

Fountain shows Notification settings saved. To stop the emails, turn the same switch off and save again.

If you also manage data pipelines, turn on Data pipeline failure in the same section. It needs permission to manage data pipelines and to view data pipeline logs.


Know When an Alert Is Sent

Fountain sends an alert when a run fails for good, not at the first problem. A run counts as failed when:

  • It still fails after the last automatic retry.

  • It fails on a source that does not retry, such as an SFTP import.

  • It cannot run because of a setup error, such as missing access to the data it needs.

A run also fails when it times out. A run times out when it waits 30 minutes without starting, or when it waits longer than its reply limit for another service, such as Pool. The default reply limit is 24 hours. A run never times out because Fountain itself is busy.


Read a Failure Email

Each email covers one failed run, so you can act on it right away.

  • The subject reads Automation failed: followed by the automation name. For a timeout, it reads Automation timed out: instead.

  • The body says when the automation stopped, in your time zone, and gives the reason in one sentence.

  • The View run button opens the run that failed.

If one setup problem stops several automations at once, you get a single email titled Your automations could not run instead of one email per automation.


Open the Failed Run

Start from the email to land on the exact run that failed.

Select View run in the email > review the run details that open in your automation logs.

The run details show the status, the reason, and what the automation was working on. To see all runs, go to Settings > Automations > Automation logs. If your company uses Supervision Center, this opens Supervision Center filtered to automations. Otherwise it opens the Automation logs list, where the Changed at (local time) column shows when each run last changed status.

A run that timed out shows the status Timed out and says what it waited for, such as Waited 1 hour for Pool. To find these runs, filter by Status > Timed out. In Supervision Center, the Status filter shows Failed and Timed out runs by default.


Get One Summary for Repeated Failures

When an automation keeps failing, you do not get an email for every run. After the first email, further failures of the same automation in the next hour arrive as one summary.

The summary tells you how many more runs failed and the most frequent reason. Select View runs to see them all.


Retry a Timed-Out Run

A run that waited for Pool may have reached Pool after all. Check before you retry, so the work is not done twice.

  1. Open the timed-out run, or its row menu in your automation logs, and select Retry.

  2. In Retry this run?, check whether Pool already processed the applicant. When one applicant matches, select Open applicant in Pool to go straight to them.

  3. If Pool did not process the applicant, select Retry anyway. Otherwise select Cancel.

A run that timed out while waiting in the queue never reached another service. When you select Retry on it, it runs again right away, with no dialog.

What to Know

  • Manual retries and test runs do not send emails. If you retry or re-evaluate a run yourself and it fails again, or a test run fails, check your automation logs.

  • Alerts are email only. They do not arrive in Slack, by text message, or inside Fountain.

  • An automation that stops running is not a failure. If an automation is turned off or never starts, no alert is sent.

  • Failing automations keep running. An alert does not pause the automation. Fix the cause or turn the automation off yourself.

  • Nobody is warned when the last person turns alerts off. Agree in your team on who keeps them on.

  • Alerts go only to active users. Deactivated users get no alerts.

Did this answer your question?