Hotjar: Session created and recording created signals not sent for ~20 minutes which affects Zapier and Slack integrations
Timeline of updates
- resolved
We want to inform our users about an incident we discovered and fixed that may have affected our Slack and Zapier integrations for Recordings and the First Recording messages in our web app. These integrations rely on "session created" and "recording created" signals which our Recordings processing service didn't send from around 14:03 to 14:16 UTC. We reverted the change that caused this issue. The integrations did not forward Recordings during that time frame, but Session Capture was not affected, so the Recordings should appear in your Hotjar Overview. Thanks for bearing with us!
From Hotjar’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.hotjar.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Hotjar, started 2023-01-10 14:51 UTC, resolved after 0 min, 1 update(s).
- Title
- Session created and recording created signals not sent for ~20 minutes which affects Zapier and Slack integrations
- Vendor
- Hotjar
- Date
- URL
- https://rewindex.com/company/hotjar/incidents/qhm06hvvk4ch
Hotjar profileRecent Hotjar incidentsAll outages on January 10, 2023Hotjar in January 2023MarkdownJSON