Malomo Outage History

A fix has been deployed and we are monitoring results.

On February 26th, our primary database failed after its internal logging system ran out of allocated disk space. As a result, our recovery infrastructure automatically switched to a backup database to maintain uptime. However, we recently discovered that because the logging system failed, the backup database was approximately two days behind in replication (replication is normally near-instant). As a result, orders and shipment records processed during that window were not present after failover. We chose not to re-import those orders because doing so may trigger unwanted duplicate events. Tracking updates will fail for those orders as a result. TO RESOLVE THIS ISSUE, you can take the following action: If you're using one of our integrated apps to trigger notifications (Klaviyo, Attentive): 1) Place a flow filter on any flows that use the Malomo:ShopifyOrderCreated event (typically Order Confirmation emails) that checks to see if a Shopify order has been placed in the last day. If yes, then proceed to trigger the flow as normal. 2) Place a flow filter on any flows that use the Malomo:ShipmentCreated event (typically Just Shipped emails) that checks to see if a Shopify order has been fulfilled int he last day. If yes, then proceed to trigger the flow as normal. 3) Once steps 1 and 2 are complete, place an order tag on any order that was placed or fulfilled between Feb 24th and Feb 26th. The tag can be anything. This will cause us to sync the order and begin tracking shipments and triggering notifications as expected. If you're using Shopify to trigger your notifications: Place an order tag on any order the was placed or fulfilled between Feb 24th and Feb 26th. The tag can be anything. This will cause us to sync the order and begin tracking any shipments as expected.