FloQast incident
Quickbooks Online Integration Refreshes Failing To Complete
FloQast experienced a minor incident on January 16, 2026 affecting Optimize the Close - EMEA and Optimize the Close - APAC and 1 more component, lasting 6h 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 16, 2026, 05:10 PM UTC
We are currently investigating an issue with the Quickbooks Online integration failing to refresh successfully.
- investigating Jan 16, 2026, 09:57 PM UTC
We are continuing to investigate this issue.
- identified Jan 16, 2026, 11:12 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jan 16, 2026, 11:33 PM UTC
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.
- postmortem Jan 21, 2026, 10:38 PM UTC
**Summary:** Customers experienced an interruption in service where QuickBooks Online \(QBO\) entities failed to refresh, preventing accurate data synchronization and resulting in failure to retrieve balances. **Root Cause:** The third-party vendor, QuickBooks Online, implemented an unannounced update to their system's request validation rules. This change caused previously successful data requests from our application to be rejected by the vendor's infrastructure, despite the underlying integration logic remaining unchanged. **Immediate Resolution:** Our engineering team identified the specific change in the vendor’s validation requirements and deployed a hotfix to adjust the formatting of our data requests. This update ensures compliance with the vendor's new standards and has successfully restored full synchronization functionality across all production environments. **Follow-up Actions:** We are implementing enhanced, vendor-specific monitoring to detect external API anomalies more rapidly in the future. Additionally, we are auditing our existing alert thresholds to ensure our teams are notified immediately if integration success rates drop below expected levels, allowing for faster response times to third-party changes.