Troubleshooting Methodology

Dev Error DB pages are written around a simple debugging workflow: match the exact error signature, identify the technology and execution context, collect safe diagnostics, test the smallest likely fix, and document the result.

What to collect before debugging

• The exact error text and stack trace with secrets redacted.
• The command, API request, CI job, editor action, or deployment step that failed.
• Tool, SDK, runtime, operating system, and provider versions when available.
• Whether the failure reproduces locally, in CI, in staging, or only in production.

Safe fix workflow

1. Reproduce the smallest failing action.
2. Compare the page evidence with official documentation or your local logs.
3. Change one variable at a time.
4. Verify the same action succeeds before expanding the change.
5. Keep a rollback path for production or shared environments.

When to pause

Pause before applying a fix if it deletes data, rotates credentials, changes billing or quotas, relaxes security controls, or touches production infrastructure without a tested rollback path.