Documentation
Viewer Workflow
Sign In Through The Viewer
The viewer is signed-in only. Start at revclust.com/get-started, submit your email, check your inbox, and finish sign-in from the emailed link.
Existing members who start from an incident link return to that incident after email verification. Brand-new accounts land on /app/apps first so they can create an app and SDK key. If the page says You don’t have access to Revclust., use an active account or contact Revclust support. If it says Could not send the email link. Try again. or Could not confirm your email. Try again., request a new link first.
Open Recent Incidents
After sign-in, open /app/incidents. That page lists the recent incidents you can open.
If your first accepted incident does not appear on /app/incidents, confirm that the upload was actually accepted first. A missing list entry can still be a viewer-access issue.
Open The Accepted Incident
The acceptance path gives you a direct incident link (viewerUrl), an incident ID (packId), or both. Open the direct link if it is present. If you only have the incident ID, open /app/incidents/<pack-id>.
/app/incidents/<pack-id>
The incident route is authenticated. If you are signed out, the viewer will require sign-in before rendering the incident.
What You Should See On The Incident Page
The incident page shows the failure kind as the main heading and then organizes the incident into a few stable sections:
| Section | What it shows |
|---|---|
Details | Triggered time, pack identifier, and capture identifier. |
Trigger | Failure kind, subject, expected values, and observed values. |
Context | App, device, OS, and network context captured with the incident. |
Timeline | Ordered event timeline for the captured incident path. |
State | Captured bounded state snapshot attached to the incident. |
The page also gives you a direct JSON download action for the accepted pack and a Back to Incidents action that returns to /app/incidents.
What Counts As A Successful Viewer Check
A successful first viewer check looks like this: you sign in with the Revclust account that owns the incident, you can open /app/incidents, the accepted incident is visible there or opens directly from the incident link (viewerUrl) or incident ID (packId), and the incident page renders without access errors.
When Viewer Access Is The Problem
If the SDK reports RevclustUploadAccepted but /app/incidents/<pack-id> sends you back to sign in, shows Access denied, or shows Incident not found, the problem is on the viewer side, not the capture side. Check that you are signed into the right account and opening the same packId that was accepted.
For viewer-specific issues, include the accepted packId, your account email, and the page that failed when you contact Revclust support. Feedback may also be available after sign-in.