Skip to main content

Troubleshoot by symptom

A useful bug report includes the app, relevant route pattern, locale, workspace alias, expected behavior, actual error/status, and build version or commit where available. Keep private content, tokens, raw credentials, and personal records out of public issues and documentation.

Glossary

Evidence levels

A source file proves an implementation exists. A passing test proves the checked behavior in its fixture. A successful build proves compilation for that commit. A deployment marker identifies delivery. A recent processor result proves a job ran. Keep these distinct when reporting product readiness or incident recovery.