FloQast Outage History

Jun 2 , 10:48 PDT Resolved - We have released a fix for this issue, and customers using Egnyte should no longer be experiencing these errors. We are continuing to monitor to ensure stability, and a Root Cause Analysis will be shared here when available. Jun 2 , 09:09 PDT Identified - The issue has been identified and a fix is being implemented. Jun 2 , 08:46 PDT Investigating - We are currently investigating reports of errors when refreshing reconciliations and uploading files for customers using our Egnyte integration.

May 20 , 12:42 PDT Resolved - A fix has been released for this issue, and customers should no longer receive these "Something Went Wrong" errors. If you continue to receive the error, refreshing your browser will resolve it. We will continue to monitor, and a Root Cause Analysis will be posted here once available. May 19 , 13:31 PDT Identified - We have identified the cause of the issue and are working on a fix. May 19 , 13:18 PDT Investigating - We are currently investigating reports of "Something Went Wrong" errors when loading pages in the application. For any affected customers, clearing your web browser's cache should allow you to access the application while our engineers address the underlying issue.

May 18 , 16:47 PDT Resolved - We have released a fix for this issue, and Trial Balances uploaded via the FloQast Connect SFTP server are now being successfully processed again. We will continue to monitor and will share a Root Cause Analysis here when it is available. May 18 , 15:56 PDT Investigating - We are currently investigating reports of Trial Balance files not being successfully processed after being sent via the FloQast Connect SFTP server for customers on our APAC database.

May 12 , 13:59 PDT Resolved - This incident has been resolved. May 12 , 13:49 PDT Monitoring - A fix has been applied to the US and EU databases and both are operating normally. We are continuing to work on restoring full functionality for the AU database. We will provide a further update once AU has been resolved. May 12 , 12:39 PDT Identified - The issue has been identified and a fix is being implemented. May 12 , 12:21 PDT Update - We are continuing to investigate this issue. May 12 , 12:13 PDT Investigating - We are currently investigating an issue affecting Request Agent. Users attempting to access the Request Agent dashboard page may find the page loading endlessly.

May 11 , 16:27 PDT Resolved - This incident has been fully resolved. US customers can access FloQast as normal. A Root Cause Analysis will be published on this page shortly. We apologize for the disruption and thank you for your patience. May 11 , 16:09 PDT Update - We are continuing to monitor for any further issues. May 11 , 15:52 PDT Monitoring - A fix has been deployed for the issue affecting US customers. We are actively monitoring to confirm full stability. May 11 , 15:31 PDT Update - We are continuing to investigate this issue. We have identified that this issue is isolated to our US region. Customers in the AU and EU regions have been confirmed as fully operational. May 11 , 15:27 PDT Investigating - We are aware of an issue causing an "Something Went Wrong" error for users attempting to access FloQast. Users may be unable to load the application or see an unexpected error on login. Our engineering team has been alerted and is actively investigating.

May 8 , 13:48 PDT Resolved - The issue affecting transaction syncing has been resolved. Transactions should now be pulling in as expected for all connected clients. If you continue to experience any issues, please contact our support team. May 8 , 08:25 PDT Update - We are continuing to investigate this issue. May 8 , 08:25 PDT Investigating - We are currently investigating an issue affecting AutoRec Matching. Users are able to upload transaction files successfully, however uploaded transactions are not appearing for matching. Additionally, clients with NetSuite connected accounts are experiencing failures when pulling transactions or 'user is currently matching' messages. We are actively investigating and will provide updates as they become available.

May 7 , 17:58 PDT Resolved - The fix for this issue has been released. Users may experience a brief delay as the backlog of queued notifications is processed. We are continuing to monitor the situation and will share a Root Cause Analysis here when available. May 7 , 16:20 PDT Investigating - We are currently investigating reports of notifications tied to Review Notes not being received

May 7 , 16:18 PDT Resolved - The fix for this incident has finished deploying. A full RCA will be shared in this posting as soon as it is available. May 7 , 11:23 PDT 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. May 7 , 09:32 PDT Update - The fix is currently being applied in parallel to all FloQast environments. We expect the full resolution to be in place very soon. May 7 , 09:01 PDT Identified - The issue has been identified and a fix is being implemented. May 7 , 07:28 PDT 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

May 5 , 13:04 PDT Resolved - The fix for this issue has been released, and users should no longer be receiving errors when navigating the Single Workflow Dashboard. We are continuing to monitor performance, and a Root Cause Analysis will be shared here when it is available. May 5 , 09:33 PDT Identified - We have identified the cause of the issue and are working on a fix. Users may still see the error when navigating between the Overview, Timeline, and Entities sections of the Single Workflow Dashboard. Closing the error will allow the page to load. May 5 , 08:53 PDT Investigating - We are currently investigating reports of errors navigating the Single Workflow Dashboard. Users may see an error message when navigating between the Overview, Timeline, and Entities sections. After closing out of the error, the page should load as expected. The All Workflows Dashboard is not affected. We will post an update here as soon as we have more information.

A fix has been deployed, and reconciliations can now be opened from the Dashboard Timeline view without error. Thank you for your patience while our team investigated. A Root Cause Analysis will be shared here when available.

Apr 23 , 15:16 PDT Resolved - We have successfully deployed a fix and confirmed that changes made through the All Entities Reconciliation Template are now syncing correctly to the Reconciliations tab. A formal Root Cause Analysis (RCA) will be shared here once it is available. If there are any recent changes made via the All Entities Reconciliation Template that you do not see applied, re-applying the template should resolve the issue. Apr 23 , 12:41 PDT Identified - We have identified the cause of the issue and are working on a fix. Apr 20 , 14:26 PDT Investigating - We are investigating an issue where changes made through the All Entities Reconciliation Template are appearing in Admin Settings but not syncing to the Reconciliations tab. Please note that the Checklist is unaffected. As a temporary workaround, navigating to the Individual Reconciliation Settings page for a specific entity and clicking Save will apply any updates to that entity.

Apr 8 , 07:55 PDT Resolved - This incident has been resolved. Apr 8 , 06:35 PDT Monitoring - A fix has been implemented and we are monitoring the results. Apr 7 , 13:00 PDT Investigating - We are currently investigating this issue.

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.

Apr 2 , 10:46 PDT Resolved - The fix for this has been deployed, and the incident has been resolved. Apr 2 , 08:47 PDT Monitoring - A fix has been implemented and we are monitoring the results. Apr 2 , 06:54 PDT Investigating - We are receiving reports of 403s when interacting with specific API endpoints such as our Trial Balance or Chart of Accounts endpoints

Mar 31 , 17:02 PDT Resolved - The fix has been deployed to all regions, and functionality is now restored. We will continue monitoring for any unexpected behavior. Mar 31 , 16:51 PDT Identified - The issue has been identified and a fix is being implemented. Mar 31 , 16:40 PDT Investigating - We are currently aware of an issue resulting in specific admin settings pages not loading.

Feb 23 , 16:00 PST Resolved - Resolution: Reverting the recent deployment fixed the issue. Feb 23 , 13:00 PST Investigating - Summary: Recent deployment of a core service caused a cascading 500 error when users attempted to access TB (Trial Balance) upload folders. The error originated from a failed HTTP request with status code 500.

Feb 23 , 07:42 PST Resolved - This issue has been resolved after a newly introduced configuration requirement was made between FloQast and OpenAI. New regional configurations are now in place, and our team has validated that matching rules can be created in all three FloQast regional databases again (US, EU, AU). Feb 23 , 07:06 PST Investigating - We are currently looking into an issue where a 500 error displays when using the AI creation method to generate a rule within the Matching product.

Feb 20 , 12:30 PST Resolved - This incident has been resolved. Feb 20 , 11:30 PST Monitoring - A fix for this issue has been implemented, preventing additional erroneous duplicate tasks from being created. Work is ongoing to correct the tasks that have already been created. Feb 20 , 11:04 PST Identified - The issue has been identified and a fix is being implemented. Feb 20 , 07:54 PST Investigating - We have identified an issue where Checklist items are erroneously assigned a new Template ID when imported via the Single-Entity or All-Entities template. When an impacted template is applied via the Admin Settings > Checklist page, the updated Template ID causes a brand-new version of the checklist item to be created in the relevant periods. For items that have been fully signed off in those periods, absolutely no sign-off data is lost on the original item, but it will appear that the item has "duplicated" since this net-new version has also been added.

Feb 12 , 07:20 PST Resolved - This incident has been resolved. Feb 12 , 06:54 PST Monitoring - A fix has been implemented and we are monitoring the results. Feb 12 , 06:51 PST Identified - The issue has been identified and a fix is being implemented. Feb 12 , 05:57 PST Investigating - We are currently investigating an issue for our EMEA and APAC customers where an error message displays when clicking on a review note.

Feb 11 , 14:07 PST Resolved - A fix has been implemented, and the issue is confirmed resolved. Feb 11 , 13:38 PST Identified - We have received reports of intermittent 500 errors, specifically in the Journal Entry Management module. We have identified the issue and are actively working on releasing the fix.

Feb 10 , 13:12 PST Resolved - This issue has been resolved, and the Transform AI Agents page is now fully operational. A Root Cause Analysis will be posted here when available. Feb 10 , 13:01 PST Identified - The issue has been identified, and a fix is being implemented. Feb 10 , 12:35 PST Investigating - We are investigating reports of issues loading the Transform AI Agents page. We will provide an update as soon as more information is available.

Jan 29 , 13:03 PST Resolved - 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. Jan 29 , 10:49 PST Identified - The issue has been identified, and a fix is being implemented. Jan 29 , 07:00 PST Investigating - 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.

Jan 16 , 15:33 PST Resolved - The fix has been deployed, and we are seeing successes in each environment once again. We will continue to monitor and follow up on this post, including a root cause analysis, as soon as it is available. Jan 16 , 15:12 PST Identified - The issue has been identified and a fix is being implemented. Jan 16 , 13:57 PST Update - We are continuing to investigate this issue. Jan 16 , 09:10 PST Investigating - We are currently investigating an issue with the Quickbooks Online integration failing to refresh successfully.

Dec 19 , 14:15 PST Resolved - Certain audit log events are not appearing within the audit log export during an impacted period.

Dec 10 , 16:56 PST Resolved - The fix for this issue has been released, and we have confirmed that linking documents to Checklist Items is working as expected. A Root Cause Analysis will be posted here when available. Dec 10 , 16:32 PST Identified - The cause of the issue attaching files to Checklist Items has been identified. We are currently applying a fix and will update this page as soon as we have confirmed the resolution. Dec 10 , 15:40 PST Investigating - We are currently investigating reports of an issue attaching files to Checklist Items.