Dutchie incident

Mobile App User Segments Missing

Minor Resolved View vendor source →

Dutchie experienced a minor incident on April 2, 2026 affecting Register, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 02, 2026, 02:20 PM UTC
Resolved
Apr 02, 2026, 02:20 PM UTC
Duration
Detected by Pingoru
Apr 02, 2026, 02:20 PM UTC

Affected components

Register

Update timeline

  1. investigating Apr 01, 2026, 06:09 PM UTC

    Status: Investigating We are aware of an issue affecting user segmentation within the Dutchie mobile app experience. Some customers may not be correctly categorized based on their mobile app activity. Our team is actively investigating and working toward a resolution. Processes such as Discounts and Marketing communications based on a customer’s Mobile App status may be affected by this. Core ordering and POS functionality remain unaffected. Affected components Register (Degraded performance)

  2. identified Apr 01, 2026, 06:49 PM UTC

    Status: Identified We have identified the cause of an issue impacting user segmentation for mobile app customers. A recent data change altered how mobile login activity is attributed, which caused certain mobile app segments to behave incorrectly. Our engineering team is implementing a fix. Discount functionality has been restored but there may still be issues associated with Mobile App Push-Notifications. Core ordering and POS functionality are not affected. Affected components Register (Operational)

  3. resolved Apr 02, 2026, 02:20 PM UTC

    Status: Resolved The data issue that caused missing customers from mobile-app based segments is now resolved. Affected components Register (Operational)