> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Finding the replay you need – Session replay pocket guide [](/pocket-guides.md)Aa [](/pocket-guides/session-replay/reverse-proxy.md)[](/pocket-guides/session-replay/watching-replays.md) # Finding the replay you need – Session replay pocket guide A month of recording gives you thousands of sessions, and no obvious way in. Scrolling the list is the worst place to start. You don't know which session matters until you've already found it. The faster routes start somewhere else and arrive at a replay. ## From an insight Every insight is data related to a set of [people](/docs/data/persons.md), and every person has recordings. Click a point on a trend, or a step in a funnel Fig. 1, and you can watch the sessions behind it. The trend or funnel tells you what happened, and the replay tells you how it happened. More than 100 unique personsView recordings2 A ana@example.com1wWratLxRfKGsXHkS…WDfk3jPZ9Gbgjto View recording J jordan@example.comtnHphQQPtYSCBRNP…8oDqFsQbw4AG6Ta View recording S sam@example.orgnrejD9nmwEPRd7PE…ASxux7Tn25y8M6h View recording P priya@example.netwmKv4hcghqoTCi3…Xq7bLm2ZfPd9Nsa View recording Fig. 1 – Click a step in a funnel and you get the people it counted, each one a click away from their recording. ## From an error Sessions and Error Tracking issues are also linked by a person's session. You can see the errors that occur during a replay, and you can also find all replays containing a given error. Just look for the View recordings button, or open the **Recording** tab on the exception you have selected Fig. 2. ![An Error Tracking issue, with the button for every recording of the issue above and the Recording tab for this one exception below](https://res.cloudinary.com/dmukukwp6/image/upload/c_crop,x_1043,y_20,w_1565,h_1550/w_1600,c_limit,q_auto,f_auto/session_from_error_light_056bf99ba7.png)![An Error Tracking issue, with the button for every recording of the issue above and the Recording tab for this one exception below](https://res.cloudinary.com/dmukukwp6/image/upload/c_crop,x_1043,y_20,w_1565,h_1550/w_1600,c_limit,q_auto,f_auto/session_from_error_dark_8efab34ebd.png)12 Fig. 2 – An Error Tracking issue: every recording of the issue from the top, this one exception's recording from the tab.Hover over the figure to learn about each element. ## Saved filters A [saved filter](/docs/session-replay/how-to-watch-recordings.md) is a question you keep asking. If you're always filtering for users whose sessions include the `user_checkout` event and have signed up in the past week, save it as a filter. It live filters for the latest events. ## Collections A [collection](/docs/session-replay/how-to-watch-recordings.md) is a set of specific recordings you put there by hand. It doesn't change unless you change it. This is useful for keeping track of sessions you want to revisit or share with your team. Common failure patterns, UI papercuts, and evidence supporting your "I told you so, the button should be on the left side" argument can be saved as a collection. ## Asking instead of filtering You can also describe what you want and let PostHog AI assemble the filter. You don't have to know which field a thing lives under, which is most of the work. You can try running any of these prompts in PostHog AI to get started: - [Users who rage clicked on the pricing page last week](https://app.posthog.com/#panel=max:!Users%20who%20rage%20clicked%20on%20the%20pricing%20page%20last%20week) - [Sessions where someone hit an error during checkout](https://app.posthog.com/#panel=max:!Sessions%20where%20someone%20hit%20an%20error%20during%20checkout) - [Recordings from people who saw the new onboarding flag variant](https://app.posthog.com/#panel=max:!Recordings%20from%20people%20who%20saw%20the%20new%20onboarding%20flag%20variant) - [Mobile sessions that ended on the signup form without submitting](https://app.posthog.com/#panel=max:!Mobile%20sessions%20that%20ended%20on%20the%20signup%20form%20without%20submitting) - [Long sessions from first-time visitors who never reached the dashboard](https://app.posthog.com/#panel=max:!Long%20sessions%20from%20first-time%20visitors%20who%20never%20reached%20the%20dashboard) - [Sessions with dead clicks on the settings page this month](https://app.posthog.com/#panel=max:!Sessions%20with%20dead%20clicks%20on%20the%20settings%20page%20this%20month) ## When there are too many to look at PostHog can watch sessions for you and report on findings. If you'd like summaries and reports, use session summaries and [scouts](/docs/self-driving/scouts.md). If you'd like to turn sessions into queryable data, use [Replay Vision](/docs/replay-vision.md) [scanners](/docs/replay-vision/scanner-types.md). We'll introduce all of them in [the next section](/pocket-guides/session-replay/replay-vision.md). See also: [How to watch recordings](/docs/session-replay/how-to-watch-recordings.md) · [Find replays with AI](/docs/session-replay/find-replays-ai.md) · [Watching replays yourself](/pocket-guides/session-replay/watching-replays.md) · [Getting a robot to watch for you](/pocket-guides/session-replay/replay-vision.md) [‹ Reverse proxy](/pocket-guides/session-replay/reverse-proxy.md)[All guides](/pocket-guides.md)p. 5 of 7[Watching replays yourself ›](/pocket-guides/session-replay/watching-replays.md)