FloQast incident
Reports of "Something Went Wrong" errors being received in various parts of the application.
Resolved after 9 hours 19 minutes, affecting Optimize the Close - US and Automate the Close - US, on April 7, 2026.
**Summary:** Clients experienced “Something Went Wrong” errors throughout certain parts of the application. **Root Cause:** As part of ongoing security infrastructure improvements, FloQast migrated services to a more robust web application firewall \(WAF\) configuration. In pre-production environments, a supplemental ruleset had been in place that, by design, took precedence over certain standard security rules — effectively masking how those rules would behave in production. When the migration to the stricter production security configuration occurred, legitimate integration traffic was inadvertently caught and blocked. **Immediate Resolution:** Engineering teams performed a full rollback of the affected deployments, restoring integration functionality for impacted customers. Once stable, the team began a careful analysis of the specific security rules to confirm that the appropriate level of restrictions was being adhered to. **Follow-up Actions:** The team is taking a deliberate approach to reintroducing the production security ruleset in monitoring mode before enforcing blocks, allowing for validation against known traffic patterns.
Affected components
Update timeline
- identified Apr 07, 2026, 02:30 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 07, 2026, 03:20 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 07, 2026, 04:35 PM UTC
Apr 7, 09:35 PDT Resolved - This incident has been resolved. Apr 7, 08:20 PDT Monitoring - A fix has been implemented and we are monitoring the results. Apr 7, 00:15 PDT Identified - The issue has been identified and a fix is being implemented.
- resolved Apr 07, 2026, 04:35 PM UTC
This incident has been resolved.
- postmortem Apr 08, 2026, 01:41 PM UTC
**Summary:** Clients experienced “Something Went Wrong” errors throughout certain parts of the application. **Root Cause:** As part of ongoing security infrastructure improvements, FloQast migrated services to a more robust web application firewall \(WAF\) configuration. In pre-production environments, a supplemental ruleset had been in place that, by design, took precedence over certain standard security rules — effectively masking how those rules would behave in production. When the migration to the stricter production security configuration occurred, legitimate integration traffic was inadvertently caught and blocked. **Immediate Resolution:** Engineering teams performed a full rollback of the affected deployments, restoring integration functionality for impacted customers. Once stable, the team began a careful analysis of the specific security rules to confirm that the appropriate level of restrictions was being adhered to. **Follow-up Actions:** The team is taking a deliberate approach to reintroducing the production security ruleset in monitoring mode before enforcing blocks, allowing for validation against known traffic patterns.
Your product runs on more than FloQast
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services