M
31
Easy Fix
MongoDB · Database Server & Atlas
MongoDB server reported: Role Not Found.
Quick Answer
Error code 31 on your MongoDB Database Server & Atlas means: MongoDB server reported: Role Not Found.. This is usually fixable — see the step-by-step guide below.
Affected Models
Likely Causes
  1. MongoDB returned code 31 (RoleNotFound) while processing this request path.
  2. Session or token context was stale, revoked, or scoped to a different tenant/project.
  3. Credentials, account state, or security policy did not satisfy authentication requirements.
How to Fix It
1
Review logs/telemetry for code 31 (RoleNotFound) and capture the exact command and parameters that triggered it.
2
Validate auth configuration in code and environment variables against the current deployment.
3
Rotate credentials if needed and run a least-privilege permission audit for this operation.
4
Re-check account/role bindings, tenant scope, and credential freshness before retrying.
5
Add monitoring for recurring RoleNotFound events so future incidents are detected and triaged faster.
Pro Tip
This is a common issue that most users can resolve without specialized tools. Try the first step before moving on to more complex solutions.
Related Error Codes
Video Guides
Loading video guides…
Search more on YouTube →