Help Center Category
Troubleshooting and known patterns
This section covers the most common reasons users think something is broken when the real issue is permissions, cache, wrong workspace, or outdated assumptions.
Articles in this section
1
What to check before reporting a bug
Before reporting a bug, confirm the current route, the active organization or workspace, whether the page was refreshed after a deployment, and whether the latest release notes describe the behavior you are seeing.
2
How to describe a problem so support can act quickly
The best issue report is short but complete. Include the route, the workspace, the expected outcome, the actual outcome, and the approximate time. If there is a visible error, send the exact text instead of paraphrasing it.