The target password changed but one consumer retained the old value

A fictional managed database account is used by two applications under approved access rules. The credential-management logs show a completed change and a successful verification against the database. One application obtains fresh credentials through its supported provider workflow, while the other loads a copy only at startup. The second application now fails authentication. A developer says the repository must be wrong and requests that the new password be sent in a team chat. Another proposes disabling every future rotation permanently. The task is to distinguish the target credential state, retrieval permissions and consumer-refresh behavior using the supplied evidence. No real secret is retrieved or changed, and no assumption is made that every provider or application uses the same cache and expiry mechanism.