Wisely incident

Campaigns, automations, and interactions services are experiencing extremely degraded performance

Minor Resolved View vendor source →

Wisely experienced a minor incident on June 5, 2023 affecting Guest Data Platform (GDP), lasting 4d 2h. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2023, 02:59 PM UTC
Resolved
Jun 09, 2023, 05:16 PM UTC
Duration
4d 2h
Detected by Pingoru
Jun 05, 2023, 02:59 PM UTC

Affected components

Guest Data Platform (GDP)

Update timeline

  1. investigating Jun 05, 2023, 02:59 PM UTC

    Campaigns, automations, and interactions services are experiencing extremely degraded performance. This affects campaigns and automations such as guest birthday/anniversary, computed properties, and incoming GDP events

  2. identified Jun 05, 2023, 03:05 PM UTC

    The issue has been identified and is being remediated.

  3. identified Jun 05, 2023, 04:11 PM UTC

    Automations are now functional and campaigns are degraded but returning to operational. Guest timeline is still delayed but engineers are continuing to work on this issue.

  4. identified Jun 05, 2023, 05:48 PM UTC

    Our engineers are continuing to work on a resolution for Guest Timeline delays.

  5. identified Jun 05, 2023, 09:55 PM UTC

    Automations are still functional, but some non-scheduled automations are experiencing a delay. Guest timeline event data is currently delayed. Our engineers have identified and are implementing a strategy to resolve the delay and catch up to real-time processing. We will continue to provide updates as they become available.

  6. identified Jun 06, 2023, 02:42 PM UTC

    Guest Data and non-scheduled automation latencies are now resolved. At this time, computed properties are degraded. Automations, Campaigns, and all other systems are functioning normally. We will continue to provide updates as they become available.

  7. identified Jun 08, 2023, 07:51 PM UTC

    All services are back to operating at full capacity.

  8. resolved Jun 09, 2023, 05:16 PM UTC

    This incident has been resolved.