This incident has been resolved. The SDK endpoints are now fully operational.
The issue was caused by a dependency update we deployed to patch a critical security vulnerability, which caused all requests to the SDK endpoints to fail. It began at approximately 13:23 UTC and was resolved at 13:48 UTC, affecting all customers using the Flows SDK.
We apologize for the disruption this caused. If you have any questions or are still experiencing issues, please reach out to support@flows.sh.
Resolved
This incident has been resolved. The SDK endpoints are now fully operational.
The issue was caused by a dependency update we deployed to patch a critical security vulnerability, which caused all requests to the SDK endpoints to fail. It began at approximately 13:23 UTC and was resolved at 13:48 UTC, affecting all customers using the Flows SDK.
We apologize for the disruption this caused. If you have any questions or are still experiencing issues, please reach out to support@flows.sh.
Monitoring
A fix has been deployed for the issue affecting the SDK endpoints. We are closely monitoring our systems to confirm full recovery.
Some users may not see their workflows until they reload the page. If you continue to experience issues, please contact our support team at support@flows.sh.
We will confirm resolution once we are satisfied that all systems are stable.
Identified
We have identified the root cause of the issue affecting the SDK endpoints. A dependency update made to patch a critical vulnerability caused every request to the SDK endpoints to return a 500 error.
Our team is currently deploying a fix, and we expect it to be in place within the next 30 minutes.
Investigating
We are aware of an issue affecting our SDK endpoints and are actively investigating. Events are not being received, and workflow data is not being delivered.
We will provide an update as soon as we have more information.
We apologize for the inconvenience.