This instability is now resolved as all components and features from the platform are back to it's normal state.

A fix has been done as the Cloud Provider has finished the nodes change and the whole Elastic Search cluster is now with up and running status. We are still monitoring this to understand why the Cloud Provider took this action or what triggered this action on the cluster.

The issue was identified and a fix is on going. The issue is related to the Elastic Search (search and indexing service) writing node and a possible update on our Cloud Provider. The writing node was blocked.

All actions executed for updated cards are going to the retry queue so they wont be lost. Reports taken on during this instability may have inconsistency. We are still investigating.