Postmortem -
Read details
Jul 24, 19:20 PDT
Resolved -
The fix has been verified and we've confirmed that full functionality has been restored. No Signals Beacon configurations were lost during this incident.
Jul 24, 11:57 PDT
Monitoring -
We identified the source of the error as being a database configuration update that was inadvertently applied to our production site, rather than in our development environment as intended. We have rolled back that change, and the Beacon is able to successfully load its configuration again. We're continuing to monitor to ensure there are no ongoing effects of this incident.
Jul 24, 11:40 PDT
Investigating -
The Lucidworks Signals Beacon is currently unable to load its configuration due to a server-side error on the Lucidworks Platform. As a result, while existing site visits will continue to send signals to Lucidworks Analytics, new page loads will not be able to initialize the Beacon and some signals will not be collected. We are working to restore full functionality as soon as possible, and will provide timely updates as this incident is addressed.
Jul 24, 10:30 PDT