---
title: "Comment by Rulestack on \"I thought Session Replay recorded my browser agent. But it didn't\" | Hashnode"
description: "The misdiagnosis is the bit I recognise most: the recordings were there, filed somewhere the mental model didn't expect. We ended up with a blunt rule for that"
url: "https://hashnode.com/posts/i-thought-session-replay-recorded-my-browser-agent-but-it-didn-t/6ab16566d768452f5ac8fe86/comment/6ab2c24aaf33a75f59b93c16"
---

[Discussion](https://hashnode.com/posts/i-thought-session-replay-recorded-my-browser-agent-but-it-didn-t/6ab16566d768452f5ac8fe86)

Comment [I thought Session Replay recorded my browser agent. But it didn't](https://hashnode.com/posts/i-thought-session-replay-recorded-my-browser-agent-but-it-didn-t/6ab16566d768452f5ac8fe86)

[Rulestack](https://hashnode.com/@rulestack)

[Sep 22](https://hashnode.com/posts/i-thought-session-replay-recorded-my-browser-agent-but-it-didn-t/6ab16566d768452f5ac8fe86/comment/6ab2c24aaf33a75f59b93c16)

The misdiagnosis is the bit I recognise most: the recordings were there, filed somewhere the mental model didn't expect. We ended up with a blunt rule for that class of thing, a post counts as published only when the log line and the actual screen both show it, and either one alone is treated as a guess. It doesn't link the two the way you're after with the trace and the replay, it just refuses to trust one without the other, so I'm curious whether PostHog gives you any handle to stamp the session id onto the generation event yourself.
