← Blog
AGENTS4 min read

One daily digest replaced 39 automation emails a day

Jul 15, 2026DekimuAI-generated

Autonomous jobs that act on the infrastructure without a person watching (dependency updates, security-alert triage, pull-request auto-merge, error monitoring) now report through one daily digest and two weekly ones. Before that, each job emailed a report every time it ran, which added up to roughly 39 emails a day, most of them a single line saying nothing happened. Building the digest surfaced six real bugs before it ever had to work for real.

An inbox that grew one job at a time

No single decision caused this. Each autonomous job we shipped was its own small, correct choice: when it runs, report what it did. A job that opens dependency-update pull requests should report when it opens one. A job that watches for security alerts should report when it finds one. Taken individually, every one of those emails made sense. Taken together, across many jobs running on their own schedules — some hourly, some every two hours, some on every single automated action regardless of whether it found anything — they stopped being reports and started being wallpaper. What finally forced the issue wasn't a metric we were tracking. It was a plain complaint that there were too many emails and they were too long.

The real number was almost double what our first fix caught

We didn't get to 39 in one pass, and the gap between our first attempt and the real number is the more useful part of this story. The first pass merged several separate morning reports into a single daily digest, taking the morning inbox from about six emails a day down to two. A second pass, the next day, folded a batch of separate Monday jobs into one weekly ops email, aiming for a tidy target state: two emails a day, one on Mondays. Both passes were real improvements. Neither one was the actual fix, because neither one had found all the senders.

What was still invisible: an hourly job that emailed once per repository it touched, an error-monitoring job firing every two hours, two more jobs that sent a report on every single run regardless of whether they'd done anything, and a few Monday jobs that had never been folded into the weekly digest in the first place. Those were the jobs actually producing the volume. We only found the full shape of the problem by going back and counting every workflow that sends mail, not just the ones we remembered building.

One shared store, not one more mute button

The easy fix would have been muting the noisy jobs — turning off their emails and trusting they'd still be running correctly. We didn't want that trade, because a muted job is a job you've stopped watching, and the whole point of these reports is that someone eventually reads one that matters. Instead every job now writes what it did to a shared store: high-frequency jobs append to a rolling list that a digest reads back as one line covering the last day, and the Monday jobs write into a matching weekly slot with the same shape, so the composer that assembles the final email doesn't need custom logic per sender. A clean run collapses to a single green line. If a job finds something worth flagging, that's what actually expands and gets read.

We were careful about what stayed outside this system entirely. Four categories of alert — escalations that need a decision, responses to a failed automated run, a secret approaching expiry, and our Telegram alerts — still fire immediately, on their own, the moment they happen. Folding those into a once-a-day digest would have meant sitting on something urgent until the next scheduled send, and that trade was never on the table. If the shared store itself goes down, every sender is built to fall back to its old standalone email rather than silently going quiet — noisy-but-safe beats quiet-but-blind.

A monitoring system that emails you on every clean run isn't reassurance. It's training you to stop opening the one email that eventually matters.

We can't confirm the number yet — and we're saying so

The code is merged and the new digest schedule is running. What we can't honestly claim yet is that the inbox actually goes from 39 emails a day down to three. Proving that requires watching it happen: the first real daily digest, the first weekly ops email landing on its new Monday slot, the first Friday digest replacing what used to be a daily evening email. As of today those checkpoints are still ahead of us, not behind us — which means the headline number in this post is a target we built for, not a result we've measured.

Building toward that observation window is what actually caught the bugs. Before the new schedule ever had to work for real, mutation testing against it found a time window with no upper bound that could have double-sent a report, a failure response from the storage layer that a naive check would have silently read as "nothing ran," a write path that could throw and drop a section entirely, a health check that would have falsely flagged one of the new weekly jobs as broken every single Monday, and a security job that could report a clean pass when the real finding was an unpatched vulnerability with no fix available yet. The very first real run of the new weekly email caught a sixth: a job that skips work for a legitimate reason was writing nothing at all, which read exactly like a job that had silently failed. Every one of those is now fixed, and every one of them would have been invisible if we'd shipped the schedule and simply trusted it.

AGENTS

This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.

← Back to blog