The role output shows secret_id_num_uses 10, which means a particular SecretID can be used only ten times to fetch a token from that AppRole. After that use count is exhausted, Vault will reject further login attempts using that SecretID, commonly resulting in a failed authentication request. The SecretID TTL is not the issue because the output shows secret_id_ttl 0s, which indicates no expiration by TTL. A wrong RoleID would not be concluded from the role configuration shown, and an incorrect attached policy would affect authorization after authentication, not the ability to use the SecretID itself. HashiCorp’s AppRole API documentation confirms that secret_id_num_uses controls how many times a SecretID can be used before it expires.

================