Cova Incident History

Our teams have confirmed the latency in the Customer service has fully resolved and errors have ceased. Thank you for your patience.

We are continuing to monitor as services normalize and will provide additional updates until fully resolved.

We are continuing to see general improvements to requests related to Customers in Cova, but as we still see some events in the backlog for services to catch up, we are continuing to monitor until we are confident this is fully resolved.

We are still seeing some intermittent issues related to the Cova Customers service, and continue to monitor until we are confident this has been resolved. Thank you for your patience.

We are seeing Customer events returning to normal service levels but will continue to monitor to ensure that this issue is fully resolved. Thank you for your continued patience.

We are seeing the Customer service is continuing to process the backlog of events. We are seeing the service continue towards a resolution but we cannot currently provide an estimate on when services will be fully returned to normal responsiveness.

We have identified and issue with the service that handles Customers in Cova. Affected users might have difficulty creating or searching for Customers in the Cova hub or the Cova app, or search results might be returned slower than normal. We aware of this issue and are currently working towards a resolution. We do not have an ETA on a solution at the moment but will provide updates as they become available.

Catalog with newly created products has been resolved, thank you for your continued patience.

Catalog with newly created products has been resolved. We will keep monitoring for stability. Thank you for your continued patience.

We are still monitoring the recovery of the issue with newly created products not appearing right away. We are seeing services process events in the queue but as we have not yet seen a full recovery, we are continuing to monitor. We will provide an update when we are confident this has been resolved. Thank you for your patience.

We are still monitoring the recovery of the issue with newly created products not appearing right away. We are seeing services process events in the queue but as we have not yet seen a full recovery, we are continuing to monitor. We will provide an update when we are confident this has been resolved. Thank you for your patience.

We have identified the Cova service that is causing newly created products to not immediately show up in the product list. We are currently monitoring the issue and waiting for services to return to normal levels. We will continue to provide updates until the issue is resolved. Thank you for your patience.

We have seen that inventory from Purchase Orders and completed sales are updating inventory in the Cova hub as expected again. No information from sales or Purchase Orders was lost during this time, only delayed in processing. We are continuing to see that newly created products are not yet showing up in the Cova Catalog. We are continuing to investigate the issue and will provide updates as they become available. Thank you for your continued patience as we investigate.

We are currently experiencing an issue where newly created products may not appear in the Cova Catalog immediately. In addition, sales processed through Cova and newly received inventory may not update product quantities right away. Our team has identified the affected services and is actively investigating the cause. We appreciate your patience and will provide updates as more information becomes available.

The incident with delays in inventory manager have been resolved.

Cova is aware of an issue that is causing delays in newly received inventory appearing in the system and pricing updates being reflected. Our team is actively investigating and monitoring the issue, and we expect it to be fully resolved within the next 15–20 minutes.

Cova is aware of an issue that is causing delays in newly received inventory appearing in the system and pricing updates being reflected. Our team is actively investigating and monitoring the issue, and we expect it to be fully resolved within the next 15–20 minutes.