Wyng incident

Experience SDK issues

Resolved after 1 day 18 hours, on October 11, 2024.

resolved Oct 21, 2024, 07:53 PM UTC

On October 11 at 2:30 PM EDT, we received reports from some customers about problems with Custom JavaScript code not running properly. At 4:19 PM EDT, we isolated the error to a problem in a recent release of the Wyng platform, and identified an available workaround for affected clients, to set the Wyng Platform version used by their experience to 1.2.165. After further investigation we determined the root cause to be some Experience SDK events were not being generated correctly, the campaign_loaded and page_loaded events. The bug was resolved with a hot-fix released on October 13, at 8:26 AM EDT. After further internal review, we have determined that this incident was avoidable. The error in logic was missed by our quality assurance processes, specifically our automated regression testing system, due to a gap in test coverage. That gap has been corrected, and we do not expect a similar issue to recur.

Started
Oct 11, 2024, 06:30 PM UTC
Resolved
Oct 13, 2024, 12:32 PM UTC
Duration
1d 18h
Detected by Pingoru
Oct 11, 2024, 06:30 PM UTC

Update timeline

  1. resolved Oct 21, 2024, 07:53 PM UTC

    On October 11 at 2:30 PM EDT, we received reports from some customers about problems with Custom JavaScript code not running properly. At 4:19 PM EDT, we isolated the error to a problem in a recent release of the Wyng platform, and identified an available workaround for affected clients, to set the Wyng Platform version used by their experience to 1.2.165. After further investigation we determined the root cause to be some Experience SDK events were not being generated correctly, the campaign_loaded and page_loaded events. The bug was resolved with a hot-fix released on October 13, at 8:26 AM EDT. After further internal review, we have determined that this incident was avoidable. The error in logic was missed by our quality assurance processes, specifically our automated regression testing system, due to a gap in test coverage. That gap has been corrected, and we do not expect a similar issue to recur.

Your product runs on more than Wyng

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →