Sessions · Guides
See where people get stuck
Every five minutes Sessions reads the journey for the places people get stuck, and gathers each place into one stuck point with everyone it happened to.
Stuck points come from the journey, so they need it switched on: Follow the journey. Two kinds also need recordings, which see the presses and dialogs your server doesn't.
What counts as stuck
| Kind | Meaning |
|---|---|
repeated-refusal | The same write sent back 3 times or more in one visit. |
loop | Back and forth between two pages: X, Y, X, Y within 3 minutes. |
slow | A page or a write that took 3 seconds or more. |
error | The server failed: a 5xx. |
gave-up | A key flow's run with no new step for its give-up time. |
abandoned-form | A dialog opened and closed with no save in between. Recorded visits only. |
rage-press | The same control pressed 3 times or more within 1.5 seconds. Recorded visits only. |
A stuck point is one kind in one place, such as a route or a key flow's step, in one environment. Each time it happens to someone is kept with it, with the person, what happened and, when it was recorded, the moment in the recording.
The list
Stuck points shows one environment at a time, the ones that came back first, then the ones that hit the most people. Pick out a kind with its pill. A stuck point's page shows its people and times over 30 days, and each time, newest first, with a link to the person's journey or the recording.
Recordings where the person got stuck are also listed under the Stuck tab of Recordings.
Resolve or ignore
Each stuck point is in one of three states:
- Open: found, and nobody has dealt with it yet.
- Resolved: you fixed it. If it happens again, it's Back, and shows among the open ones again.
- Ignored: it stays out, even when it's seen again.
The tabs are Open (with the ones that are back), Back, Resolved, Ignored and All.
Members whose role may triage resolve or ignore a stuck point from its page, with a note, and can reopen it later. A resolved one's days are split at the fix, so you can see whether it worked.
Keeping the list useful
- Skip routes that are no one's step, such as autosaves and polling, with
journey.skip_routes. - Keep your own people out: list them in your project's Settings → Your own people, and mark their pages with
internal: true. - Tell server errors from refusals: if your app shows a toast for a failed write instead of an error page, set
journey.server_error_toaststo how those toasts begin.