If you have upgraded to OBS 28 and are using the compat version of obs-websocket, then this is normal behavior. Previously, I modified the regular (non-compat) version of obs-websocket to support this event.
At the moment I’m trying to get rid of most of the bugs while switching to the v5 version of obs-websocket. But perhaps there are still problems in the obs-websocket-dotnet library itself, which I use…
I’ll probably try to update the compat version of the library first and release a new version with it.
I can no longer imagine how to use replays in OBS without these notifications 😅