Troubleshooting
Turn an error into useful information for finding its cause.
On this page
Reproduce the problem
Record the action that triggers the error and check whether it happens consistently or only under specific conditions. Test in development and preserve the configuration that showed the problem.
Collect the context
- Resource name and version; framework and server version.
- The first complete error message, with the time and where it appeared.
- Reproduction steps, expected result and observed result.
- Changes made before the issue, without passwords or tokens.
Preserve your data
Avoid deleting tables or replacing files to fix an error before identifying its cause. Return to a known copy in the test environment when you need to compare behaviour.
