Critical incident

FloQast: Reports of "Something Went Wrong" errors being received in various parts of the application.

Affected: Optimize the Close - US, Automate the Close - US

Current status of FloQast: Operational — live FloQast status

Timeline

1. Apr 7, 2026, 07:15 UTC
   identified
   The issue has been identified and a fix is being implemented.
2. Apr 7, 2026, 15:20 UTC
   monitoring
   A fix has been implemented and we are monitoring the results.
3. Apr 7, 2026, 16:35 UTC
   resolved
   This incident has been resolved.
4. Apr 8, 2026, 13:41 UTC
   postmortem
   **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.

Updates as published by FloQast (original).