Who and where?
One user or many; one entry or a folder; one workspace or all; one platform or mixed clients.
Help center / RDM triage
Diagnostic serviceMake the issue small enough to test.
A strong triage record distinguishes impact from cause and identifies the smallest safe comparison that can eliminate a layer.
First-pass classification
When did it begin?
Exact time, first known occurrence, last known success, frequency, and recent changes.
What work is blocked?
Business task, urgency, safe workaround, affected systems, and escalation owner.
Comparison matrix
| Compare | What it may isolate |
|---|---|
| Affected vs. unaffected user | Role, profile, local client, permissions, or user-specific settings |
| Affected vs. unaffected entry | Entry configuration, credential, target, or inherited setting |
| One platform vs. another | Client implementation, integration, or operating-system dependency |
| Current vs. previous version | Release change, configuration migration, or unrelated coincidence |
Safe diagnostic sequence
Preserve the failing state, capture evidence, compare a known-good case, change one variable, validate the result, and record what the test proves.
- State the hypothesis in one sentence
- Choose a reversible low-risk test
- Record before and after behavior
- Restore the baseline when appropriate
- Escalate with evidence if the layer is external
Triage FAQ
Should we reinstall first?
Usually not. Reinstallation can erase useful state and changes multiple variables. Capture versions, settings, logs, and a comparison first.
What if the error is intermittent?
Track timestamps, network context, user, entry, target, and prerequisite path. Patterns often appear when observations are normalized.
Bring the evidence you have.
We will help identify the next useful comparison.