Major incident

FloQast: Lambda Errors and Runtime Errors Experienced Throughout the Application

Affected: Platform - EMEA, Platform - APAC, Platform - US

Current status of FloQast: Operational — live FloQast status

Timeline

1. May 7, 2026, 14:28 UTC
   investigating
   We are currently investigating an issue where various functions within the FloQast application are erroring out, showing either a Lambda error or a Runtime error. This is being treated with the highest priority
2. May 7, 2026, 16:01 UTC
   identified
   The issue has been identified and a fix is being implemented.
3. May 7, 2026, 16:32 UTC
   identified
   The fix is currently being applied in parallel to all FloQast environments. We expect the full resolution to be in place very soon.
4. May 7, 2026, 18:23 UTC
   monitoring
   The fix has been initiated, and we are monitoring the results. We are aware of some errors still occurring due to warm lambdas which have not fully finished restarting yet. If a service is used and a lambda that has not been fully restarted yet is invoked, an in-app error may still occur.
5. May 7, 2026, 23:18 UTC
   resolved
   The fix for this incident has finished deploying. A full RCA will be shared in this posting as soon as it is available.
6. May 14, 2026, 22:02 UTC
   postmortem
   **Summary:** On May 7, 2026, from approximately 07:15 AM to 05:21 PM PT, customers across all regions experienced failures in automated workflows and email notifications within FloQast, resulting in jobs failing to execute as expected. **Root Cause:** A routine update from our cloud infrastructure provider changed how certain internal network traffic was handled. A prior update within our platform had not been fully applied across all parts of our environment, which created a conflict with the provider's change. Affected workflows failed immediately rather than completing normally. **Immediate Resolution:** The infrastructure update was rolled back to a prior stable configuration, and a process was run to fully refresh the affected workflows across all regions. All three regions were subsequently returned to normal operation. **Follow-up Actions:** We are taking several steps to strengthen our resilience to infrastructure changes of this kind. Going forward, updates from our cloud provider will be validated in a dedicated test environment before reaching production, giving us earlier visibility into any compatibility issues. We are also enhancing our internal monitoring to provide greater coverage across our infrastructure, and we are improving how we receive and act on cloud provider advisories so our engineering team can respond proactively to changes that may affect our environment.

Updates as published by FloQast (original).