Incidents | Flows Incidents reported on status page for Flows https://status.flows.sh/ https://d1lppblt9t2x15.cloudfront.net/logos/5a00a0ab2538f49730d29bbc07f8b7cd.png Incidents | Flows https://status.flows.sh/ en Degraded performance https://status.flows.sh/incident/606277 Fri, 20 Jun 2025 09:42:00 -0000 https://status.flows.sh/incident/606277#507c2fc67b9d24436b41ccfe86254729d55c455338c58c1a5e42b9216b9ea97f Everything is back to normal, the issue has been resolved, and the event queue has finished processing. Degraded performance https://status.flows.sh/incident/606277 Fri, 20 Jun 2025 08:48:00 -0000 https://status.flows.sh/incident/606277#46fbe492a5223ae763d9b7784ac9c78ce9fb1bf34deb7357ade0dfb2a233a6d4 A misconfigured deployment caused a backlog in our event processing system, resulting in a long queue that is now being processed. Backend recovered https://status.flows.sh/ Wed, 18 Jun 2025 08:38:29 +0000 https://status.flows.sh/#f904fa99b0ddefd5764e7b71eefd041735ede69a670baa247d1b3fd5a2219ce3 Backend recovered Backend went down https://status.flows.sh/ Wed, 18 Jun 2025 08:35:29 +0000 https://status.flows.sh/#f904fa99b0ddefd5764e7b71eefd041735ede69a670baa247d1b3fd5a2219ce3 Backend went down Backend recovered https://status.flows.sh/ Tue, 10 Jun 2025 08:37:20 +0000 https://status.flows.sh/#dc85ab672f33b8c09a28f08090717a38ffe248c618db1578f929f3cea48d2f03 Backend recovered Backend went down https://status.flows.sh/ Tue, 10 Jun 2025 08:34:13 +0000 https://status.flows.sh/#dc85ab672f33b8c09a28f08090717a38ffe248c618db1578f929f3cea48d2f03 Backend went down Database migration https://status.flows.sh/incident/594590 Sat, 31 May 2025 09:15:22 +0000 https://status.flows.sh/incident/594590#d0513fb2a90451fcfa6f861b13bb15aa99769d8a76b90025f5fd693860394443 Maintenance completed Database migration https://status.flows.sh/incident/594590 Sat, 31 May 2025 09:15:22 +0000 https://status.flows.sh/incident/594590#d0513fb2a90451fcfa6f861b13bb15aa99769d8a76b90025f5fd693860394443 Maintenance completed Flows application recovered https://status.flows.sh/ Sat, 31 May 2025 09:10:48 +0000 https://status.flows.sh/#f8d1a084054677331d2f96299914d56401142e3fe7a31615acdd492a8ceefc7f Flows application recovered Backend recovered https://status.flows.sh/ Sat, 31 May 2025 09:10:30 +0000 https://status.flows.sh/#cf73b304548c5db4745f7abb5ce6f362e0ffb91ac67ec6c99bfdcb3d16b5ddcb Backend recovered Flows application went down https://status.flows.sh/ Sat, 31 May 2025 09:01:49 +0000 https://status.flows.sh/#f8d1a084054677331d2f96299914d56401142e3fe7a31615acdd492a8ceefc7f Flows application went down Backend went down https://status.flows.sh/ Sat, 31 May 2025 09:01:29 +0000 https://status.flows.sh/#cf73b304548c5db4745f7abb5ce6f362e0ffb91ac67ec6c99bfdcb3d16b5ddcb Backend went down Database migration https://status.flows.sh/incident/594590 Sat, 31 May 2025 09:00:22 -0000 https://status.flows.sh/incident/594590#7b232ab6fc22e9a03adb98b88b28cd464316bfcd487faed11d260847cbd74458 We’ll be performing a database migration to a faster service to support our growing scale. During this time, the application and SDK api will be temporarily unavailable. Database migration https://status.flows.sh/incident/594590 Sat, 31 May 2025 09:00:22 -0000 https://status.flows.sh/incident/594590#7b232ab6fc22e9a03adb98b88b28cd464316bfcd487faed11d260847cbd74458 We’ll be performing a database migration to a faster service to support our growing scale. During this time, the application and SDK api will be temporarily unavailable. Degraded performance https://status.flows.sh/incident/582600 Wed, 28 May 2025 07:15:00 -0000 https://status.flows.sh/incident/582600#5992b03751d2896ba10e44433eebf0f7c87630b1976306e0e50b49a59db6e87f We've resolved the root issue and systems are now recovering. Unfortunately, some user state updates were lost, so workflows that were completed or closed during the performance degradation may reappear. We're sorry for the disruption and appreciate your patience as things return to normal. Degraded performance https://status.flows.sh/incident/582600 Wed, 28 May 2025 07:15:00 -0000 https://status.flows.sh/incident/582600#5992b03751d2896ba10e44433eebf0f7c87630b1976306e0e50b49a59db6e87f We've resolved the root issue and systems are now recovering. Unfortunately, some user state updates were lost, so workflows that were completed or closed during the performance degradation may reappear. We're sorry for the disruption and appreciate your patience as things return to normal. Backend recovered https://status.flows.sh/ Wed, 28 May 2025 07:09:30 +0000 https://status.flows.sh/#9b9cd7f04099c253df5f33ce891e6a01d5939e51fb94ee88652a70edd93ba386 Backend recovered Website recovered https://status.flows.sh/ Wed, 28 May 2025 06:59:58 +0000 https://status.flows.sh/#d7f332ae23084ece86edc53c023e4e60222416742f1784e55c6e3dd851347a3b Website recovered Backend went down https://status.flows.sh/ Wed, 28 May 2025 06:54:29 +0000 https://status.flows.sh/#9b9cd7f04099c253df5f33ce891e6a01d5939e51fb94ee88652a70edd93ba386 Backend went down Website went down https://status.flows.sh/ Wed, 28 May 2025 06:53:40 +0000 https://status.flows.sh/#d7f332ae23084ece86edc53c023e4e60222416742f1784e55c6e3dd851347a3b Website went down Degraded performance https://status.flows.sh/incident/582600 Wed, 28 May 2025 06:35:00 -0000 https://status.flows.sh/incident/582600#439a725ad0f8daba2523a121659a0a0b44e07f29ebb02955015154f43eb3d438 Some of our services experienced a degraded performance. Degraded performance https://status.flows.sh/incident/582600 Wed, 28 May 2025 06:35:00 -0000 https://status.flows.sh/incident/582600#439a725ad0f8daba2523a121659a0a0b44e07f29ebb02955015154f43eb3d438 Some of our services experienced a degraded performance. Complete downtime https://status.flows.sh/incident/526513 Tue, 11 Mar 2025 15:36:00 -0000 https://status.flows.sh/incident/526513#29aaf50e3d26052efad46d3c76c369ef2c25b77a858932ccb491b5339e9508a6 We are back! All our services should be up and running. Thanks for bearing with us. Complete downtime https://status.flows.sh/incident/526513 Tue, 11 Mar 2025 15:36:00 -0000 https://status.flows.sh/incident/526513#29aaf50e3d26052efad46d3c76c369ef2c25b77a858932ccb491b5339e9508a6 We are back! All our services should be up and running. Thanks for bearing with us. Complete downtime https://status.flows.sh/incident/526513 Tue, 11 Mar 2025 15:36:00 -0000 https://status.flows.sh/incident/526513#29aaf50e3d26052efad46d3c76c369ef2c25b77a858932ccb491b5339e9508a6 We are back! All our services should be up and running. Thanks for bearing with us. Complete downtime https://status.flows.sh/incident/526513 Tue, 11 Mar 2025 15:21:00 -0000 https://status.flows.sh/incident/526513#a3e36fd2cb3cab2ed5e6ae589d665da70e4ecf2686b6ec38d3fe169d0dc3aec9 High spike in traffic to our services overloaded our infrastructure. We are working to fix the problem as quickly as we can. Complete downtime https://status.flows.sh/incident/526513 Tue, 11 Mar 2025 15:21:00 -0000 https://status.flows.sh/incident/526513#a3e36fd2cb3cab2ed5e6ae589d665da70e4ecf2686b6ec38d3fe169d0dc3aec9 High spike in traffic to our services overloaded our infrastructure. We are working to fix the problem as quickly as we can. Complete downtime https://status.flows.sh/incident/526513 Tue, 11 Mar 2025 15:21:00 -0000 https://status.flows.sh/incident/526513#a3e36fd2cb3cab2ed5e6ae589d665da70e4ecf2686b6ec38d3fe169d0dc3aec9 High spike in traffic to our services overloaded our infrastructure. We are working to fix the problem as quickly as we can.