BrowserOps Failed Journey
Use when a browser journey span fails or screenshot/accessibility evidence is missing.
Linked toolsok
Commandsok
BrowserOpsTraceMonitor
Symptoms
- browserops span failed.
- Screenshot evidence ref is absent.
- Journey stopped before finish span.
Likely Causes
- Target route failed to render.
- BrowserOps adapter did not link artifact refs.
- Protected target rejected the journey.
Checks
- Open BrowserOps run evidence if public-safe.
- Inspect /api/v1/traces/{traceId}/timeline.
- Check route compliance for the target service.
Evidence To Collect
- browser run ID
- screenshot ref
- route URL
- accessibility summary
platphormctl Commands
platphormctl harness run trace-propagation-check --dry-run platphormctl trace report <traceId>