Awesome! That's a definite gap in what I described. Container health and application health aren't the same thing — a container can report healthy while a connection pool inside it is still holding a stale secret from before the restart, especially if the pool doesn't force re-authentication on reconnect. SELECT COUNT(*) told me the data survived. It didn't tell me every service was actually serving traffic on the new credential versus a cached one. Those are different claims, and I was only checking the first. Folding this in going forward: an actual read/write check per dependent service, not just a row count or a container status, before calling a rotation done. Thanks Mateo!