Hightouch: Customer Studio journeys - “Journey execution blocked” errors
Timeline of updates
- resolved
Between 1:12PM PT (on January 14th) and 6:21AM PT (on January 15th), some Customer Studio journeys may have failed with “Journey execution blocked” errors. As a result, journey syncs may have been delayed, but no data loss has occurred. We have identified and resolved the issue. All functionality has returned to normal.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
29feda2bc728afcf…
Impact, status and times are the vendor’s own, as last archived. View on status.hightouch.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Hightouch, started 2026-01-15 14:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Customer Studio journeys - “Journey execution blocked” errors
- Vendor
- Hightouch
- Date
- URL
- https://rewindex.com/company/hightouch/incidents/8g7rft6jlht3
Hightouch profileRecent Hightouch incidentsAll outages on January 15, 2026Hightouch in January 2026MarkdownJSON