Find and triage issues
See the problems that frustrate your visitors, read the evidence behind one, and mark it resolved or ignored.
Flamio On-Live groups repeated problems on the same element or page into one issue, and ranks issues by how much they hurt. Use Issues to pick what to fix, read the evidence, and mark what you fixed.
Before you begin
- On-Live is enabled and has recorded sessions. See Install the web SDK.
- Any role can read issues. To Resolve, Ignore or Reopen an issue, you need the Editor, Admin or Owner role. See Team and roles.
Find the issues that hurt most
Open Issues
In the sidebar, under Flamio On-Live, click Issues. The Detected issues tab opens by default: Recurring problems ranked by impact.
Choose the period and the population
Set the period, the version and the Traffic control in the filter bar. The header then counts the issues, for example 12 open issues, or reads No open issues — all clear. The counts cover the population you picked — people by default.
Sort the list
Click a column header to sort:
| Column | What it shows |
|---|---|
| Problem | The friction type and the element, for example Rage Click on "Add to cart", with the page under it. |
| People (or the population you picked) | How many people hit it, and in how many visits. |
| Occurrences | How many times it happened. |
| Continued | Share of affected visits where the visitor kept going instead of leaving, and when it was last seen. |
| Impact | The default sort, highest first. Combines how many people are hit, how often, and how many leave afterwards. |
A New badge marks an issue first seen inside the period. A Regressed badge marks one that came back after it was resolved.
Include one-off problems
By default the list leaves out problems that only one person hit. Tick Include single-user issues to see them too.
Open an issue
Click a row.
Read an issue
The issue page follows the same filter bar as the list, so its numbers match the row you clicked.
- The header shows the severity (High, Medium or Low), the status, the friction type and element, the page, First seen and Last seen, and the Impact score.
- Flami verification sits under the header. See Check whether an issue is real.
- The counters:
- Affected people (named after the population you picked) — distinct people who hit it at least once.
- Visits — visits in which it happened.
- Continued — share of affected visits where the visitor kept going.
- Exit after — share of affected visits that ended right after it.
- Page LCP (p75) — on a slow-page issue only: how fast the page's main content appears for three loads in four.
- Why this matters — a written summary of the issue across all time, how many people it affects, how many leave after it, and the console or network errors seen alongside it.
- Example sessions (N) — the visits where it happened. Click any row: the replay opens already at that exact moment. An EXIT badge marks a visit that ended right after the problem.
Click Back to Issues to return to the list. For the friction names you see, see Friction types.
Resolve, ignore or reopen an issue
Mark the issue
Open the issue. At the top right of the header, click Resolve when you fixed it, or Ignore when it is not worth fixing. The status pill changes at once — there is no confirmation.
See issues by status
Back on the list, switch the Issue status control between Open, Resolved and Ignored. The header counts the view you are on, for example 3 resolved issues.
Undo a decision
Open the issue and click Reopen.
A resolved issue that happens again comes back to Open on its own, with a Regressed badge. An ignored issue stays ignored.
An issue has a status only. There is no assignee, snooze or due date, and no export to a task tracker. To check whether an issue is real before you act, use Flami verification; it never changes the status.
Review errors
The Errors tab next to Detected issues lists JavaScript errors and failed network requests, grouped by error.
- Sort by people, Occurrences or Last seen, and switch between Open, Resolved and Ignored like issues.
- Click an error to open its details: the kind (JS error or Network), the request and status, the page, Visits, Occurrences, a Sample message, and every occurrence — each opens the replay at that moment.
- Resolve, Ignore and Reopen work the same way as for issues.
Result
You know which problems hurt your visitors most, you have watched them happen, and the list shows what is still open.
Related
- Check whether an issue is real
- Friction types
- Watch a visit replay
- Get a daily digest — new and growing critical issues every morning