FloQast incident
Issues Accessing AutoRec and AI Matching via the Folders tab
FloQast experienced a minor incident on January 29, 2026 affecting Automate the Close - EMEA and Automate the Close - APAC and 1 more component, lasting 6h 3m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 29, 2026, 04:54 PM UTC
We are currently investigating reports of issues accessing AutoRec and AI Matching via the Folders tab. These modules remain functional and can be accessed from the Reconciliations tab as a workaround. Our engineering team is actively working to identify the root cause, and we will provide an update as soon as possible.
- identified Jan 29, 2026, 06:49 PM UTC
The issue has been identified, and a fix is being implemented.
- resolved Jan 29, 2026, 09:03 PM UTC
We have released a fix for this issue, and AutoRec and AI Matching can now be accessed from the Folders tab successfully. We are continuing to monitor for any further issues, and a Root Cause Analysis will be posted here when available.
- postmortem Feb 02, 2026, 11:48 PM UTC
**Summary:** Clients experienced navigation failures and error messages when attempting to access AI Matching, AutoRec Matching, AutoRec Amortization, and AutoRec Depreciation through the Folders page. Impacted users were able to load these modules from the Reconciliations tab. **Root Cause:** An update inadvertently changed how certain components were initialized. When users accessed these modules from the Folders page, a necessary navigation component was not properly loaded, leading to system errors during attempts to open the modules. **Immediate Resolution**: Engineering teams identified the problematic update and reverted the changes to a previous stable state. This restoration of the original loading sequence immediately resolved the navigation failures across all environments. **Follow-up Actions:** To prevent similar occurrences, the team is implementing enhanced automated regression testing specifically for secondary navigation paths and cross-module interactions. Additionally, internal review processes for shared application components are being updated to ensure architectural changes do not impact dependent modules.