Skip to content

Troubleshooting and known patterns

What to check before reporting a bug

This section covers the most common reasons users think something is broken when the real issue is permissions, cache, wrong workspace, or outdated assumptions.

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.

A large share of reported problems come from stale browser assets, wrong workspace context, incomplete setup, or changes that were already documented publicly.

Key points

  • Refresh the page or reopen the app.
  • Confirm you are in the correct workspace.
  • Check the release notes page.
  • Capture the exact error text and route if the issue is still real.