On 9 June 2026, millions of Crédit Agricole customers received a push notification on their Ma Banque app: “Test Cédric”. Two words, no context, a link that led nowhere. An internal notification sent by mistake to all 27 million users. The wave of simultaneous logins from curious customers brought the app down straight after, with more than 7,700 reports on Downdetector around 4:30 pm.
This is the classic mistake of any CRM or marketing automation team: a message designed for a test environment, sent in production. One wrong target configuration, and the whole database receives it. The scenario is trivial, and yet it happens regularly, at every scale.
This kind of incident is avoidable with simple controls: strict separation of test and production environments, two-person validation before any push send, and an approval workflow for every high-volume message.
On the CRM projects I work on, Adobe Campaign, Salesforce, Imagino, environment separation comes up again and again. I have already written about the importance ofanonymising test databases to avoid exactly this kind of drift. A workflow tested on real data, in a poorly isolated environment, can trigger real messages to real customers. At 27 million, that makes a lot of noise.
The rule I apply every time: anything that looks like a message, email, SMS or push, has to be validated in an environment whose database is either empty or made up only of addresses whitelisted by the team. Never on the production database, not even “just to test”.
What stands out in this incident is Crédit Agricole’s response. Instead of a cold, defensive statement, the bank renamed its social accounts “Cédric Agricole” and owned the incident with humour. A bug turned into goodwill. That is exactly the stance described in my article on handling difficult situations : own what happened, do not hide, stay the calmest professional in the room.
The most expensive technical debt is often the one nobody budgeted for: a missing approval workflow, a badly configured test environment, a safeguard that was never built. Cédric should have had a safety net. So should the team that failed to give him one.
Separating test and production environments is one of the points I check in every audit. Free scoping call, no commitment.
Contact →