Resolved after 2 hours 59 minutes, affecting Optimize the Close - EMEA and Optimize the Close - APAC and 1 more, on February 23, 2026.
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.
Affected components
Update timeline
- resolved Feb 24, 2026, 12:00 AM UTC
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.
- investigating Mar 02, 2026, 04:58 AM UTC
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.
- resolved Mar 02, 2026, 05:00 AM UTC
Resolution: Reverting the recent deployment fixed the issue.
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