Getting Help
Find answers fast, troubleshoot common issues, and route to the right support channel.
Overview
Use this page when work is blocked.
The goal is fast triage and fast escalation with complete context.
Key Concepts
Symptom: observable failure, such as sign-in failure or slow load
Reproduction: steps that reliably recreate the issue
Scope: Account, Organization, and Project context for the issue
Evidence: error text, timestamps, and screenshots (redacted)
How It’s Used
Start with self-serve triage for common symptoms.
Escalate to support when reproduction is consistent and evidence is captured.
Benefits
Faster resolution through consistent triage
Less back-and-forth with support
Better auditability of what occurred and when
Setup Steps
Troubleshoot by symptom
Pick the closest match:
Sign-in and access: Login Problems
Slow pages and timeouts: Performance Optimization
Unexpected behavior: Common Issues
Specific errors: Error Messages
Network problems: Connectivity Issues
Data problems: Data Quality Issues
Best Practices
Include the minimum evidence set for support triage:
Intent: what action was attempted
Scope: Account + Organization + Project + page
Reproduction: shortest sequence that reproduces the issue
Exact error text (copy/paste)
Timestamp with time zone
Screenshot or recording (redact sensitive data)
Browser + operating system
Do not share passwords, API tokens, or client or customer PII.
Service status:
If multiple people are affected, check status first:
Summary
The fastest route is search → symptom triage → escalation with complete evidence.
Related:
Last updated