The four days no email went out
Every email Clienzo sent failed for four days — receipts, support replies, welcome emails. Nothing crashed, nobody complained. How an errors page caught it.

On October 11, the errors page in Clienzo’s admin showed something new: “Platform email failed”, twice.
It was not twice. It was everything.
What happened
Clienzo sends email through Brevo. Brevo has a security setting called Authorised IPs: only requests from listed IP addresses are accepted. It was switched on.
Clienzo’s servers run on Google Cloud Run, which sends outgoing traffic from addresses that are not fixed. Once requests started coming from an address that was not on the list, Brevo rejected them with a 401 that mentioned an “unrecognised IP address”.
Looking back through the logs, the last successful email was a welcome email on October 6. From October 7 to October 11, every send failed — 175 of them. Most were notifications about spam hitting the website’s contact form, but in between were billing and support emails that never arrived.
Why nobody noticed
Nothing crashed. The app kept working; sending email is a side effect of other actions, and a failed side effect does not stop the main one. A customer who does not receive an email usually does not write in to say so. They just assume you never sent it.
The fix
The fix was a single switch: turn off IP blocking in Brevo. The alternative was routing all outgoing traffic through one fixed address, which costs a monthly fee and adds a moving part on both servers — not worth it for this.
A test email afterwards went through, and the error group stopped growing.
What actually saved me
Two weeks before, I had built a small error tracker into Clienzo’s admin: every logged error goes into an “errors” list, grouped, with an email alert for new ones. Without it, I would have found this from a confused customer, much later.
And one rule, now written down: a 401 from an email provider that mentions an IP address is never a code bug. Rotating the API key will not fix it.
Next in this series: what platform reviews taught me about planning launches.
related
The Meta App Review trap: every permission approved, login still broken
Clienzo passed Meta App Review, and Facebook Login still refused everyone except me. The fix was one permission that the API said was already live.
An AI that drafts your posts, and code that checks its facts
Autopilot researches trends for a business and drafts next week's posts. The interesting part is the fact check — done in code, not by asking the model nicely.
Shipping an MCP server for a small SaaS
Why Clienzo can be used straight from Claude, what the MCP server exposes, and what it took to support both API keys and one-click OAuth.