# Users not progressing through journeys

- Provider: [OneSignal](https://down.guide/providers/onesignal)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 39m
- started 2026-07-01 22:11 UTC
- id: DWN-b8f79d4f77
- Official page: https://status.onesignal.com/incidents/01KWFVRY5FXD10A5QSXV9Z3TDM

## Updates from OneSignal
### 2026-07-01 22:11 UTC: identified
We have identified the root cause and are working towards a resolution. Customers may experience users not progressing through their Journeys
We will provide another update in 30 minutes.

### 2026-07-01 22:39 UTC: monitoring
We have performed the necessary mitigation and customer journeys are now progressing successfully. Some customers may experience a 5-10 minutes lag

### 2026-07-01 22:50 UTC: resolved
The issue has been resolved. All impacted systems are now operating normally.

From the builder: does your app depend on OneSignal? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=onesignal) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention OneSignal.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-b8f79d4f77), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.