Hotjar: Survey responses with User Attributes containing datetimes are not triggering Zaps in Zapier

What to do

Check whether you use Hotjar in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 18h 33m it lasted.
Anything that failed between 2024-04-24 20:20 UTC and 2024-04-25 14:53 UTC may need a replay.
Subscribe to Hotjar's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hotjar works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingApr 24, 2024, 8:20 PM UTC
We're investigating an issue with new survey responses, which are not triggering Zaps in Zapier. Our engineers are working to fix the issue ASAP, we will post updates to status.hotjar.com as we have them. Thanks for bearing with us!
provider
identifiedApr 25, 2024, 10:20 AM UTC
We've identified the root cause of this incident, and a fix is being developed! We'll post an update to let you know when we're deploying and monitoring the fix. Thanks again for bearing with us!
provider
resolvedApr 25, 2024, 2:53 PM UTC
This incident is now resolved. Thank you for your patience!
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Hotjar still down?

No, this incident was resolved 2024-04-25 14:53 UTC. For Hotjar's live state, see https://down.guide/hotjar.

How long did it last?

18h 33m, from 2024-04-24 20:20 UTC to 2024-04-25 14:53 UTC, by the times Hotjar posted.

What was affected?

Hotjar named in us.

What caused it?

Hotjar hasn't published a root cause. If it does, it shows here.

Where does this come from?

Hotjar's official status page, https://status.hotjar.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.