This is now resolved. As part of ongoing security hardening, we tightened how we validate the domains that may embed Replay, and that change didn't account for all existing integrations — some customers embedding activities through an LMS (SCORM / iframe) saw a "refused to connect" error. We've deployed a fix and embedded activities are loading normally again. No data was affected, and no action is needed on your end. We're sorry for the disruption.
