All of the content has caught up to expected behavior.
If you encounter any other issues, please open a new support case by going to Spark.Bazaarvoice.com
We have seen our indexing systems return to normal processing. We are working on getting data caught up. Bazaarvoice engineering will continue to monitor the progress.
Next update by 3pm CST October 5th 2017
Our engineering team is working on closing the gap for stale content being displayed as well as ensuring the catalog exports are current. The latest fix should help data catch up faster.
Next update by 10am CST October 5th 2017
Our engineering team has found a discovered a regression from our latest change. We are working on applying a fix to the regression.
Next Update by 11pm CST October 4th 2017
Bazaarvoice engineering has pushed out the changes and we are monitoring the results.
Next update by 7pm CST October 4th 2017
Bazaarvoice engineering is completing work needed to push out the additional code change needed. Once this particular change passes our QA process, we will proceed to push this change live and monitor the progress.
Next update by 5pm CST October 4th 2017
Bazaarvoice engineering team is working on an additional code change that is needed to resolve.
Next update by 2pm CST October 4th, 2017
The Bazaarvoice engineering team has applied a patch to fix this issue. Due to the large amount of data, there could be some time before everything returns to normal. We will continue to monitor this issue and we will provide an update on the progression of this fix tomorrow.
Next update by 10am CST October 3rd 2017
Our Bazaarvoice engineering team believes they have discovered the root cause of this issue and is currently investigating on the best steps to fix this issue.
Next update by 7pm CST October 2nd 2017
Bazaarvoice is still investigating the root cause of this issue.
Next update by 3pm CST October 2nd, 2017
Bazaarvoice engineering has detected an issue with content display being stale as well as client feed exports being stale with some clients.
We are currently investigating this issue.
Next update by: 12pm CST October 2nd, 2017