Email spam on repeated scheduled workflow failures in CI

By Kaveh Alemi·Latchkey

GitHub emails the workflow author when a scheduled run fails. A cron that fails every night sends a daily failure email, which quickly becomes noise. Fix the underlying failure, or route alerts to a channel and mute per-run email.

What this error means

You receive a "Run failed" email every day from the same nightly workflow, and the volume makes it easy to ignore a genuinely new failure.

[owner/repo] Run failed: nightly workflow run
Scheduled run of "nightly" failed on main.
# ...arrives every 24 hours while the job stays broken.

Common causes

A persistently failing scheduled job

Each failed cron slot triggers a notification email, so a chronically broken nightly job spams daily.

Per-run email notifications enabled

Default Actions notification settings email you on every failed run you author.

How to fix it

Fix the failure or route alerts

1. Resolve the underlying nightly failure so it stops emailing.
2. Send failures to a Slack or issues channel instead of relying on email.
3. Adjust GitHub notification settings for Actions email if needed.

- if: failure()
  uses: some/slack-notify-action@v2
  with:
    channel: '#ci-alerts'

Open a tracked issue on failure instead of email

Create or update a single issue on failure so repeated failures dedupe into one place rather than many emails.

How to prevent it

• Do not leave scheduled workflows failing indefinitely.
• Route cron alerts to a channel that dedupes.
• Tune Actions email notification preferences.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions