FloQast incident

500 error displays when AI generating a rule within Matching.

Minor Resolved View vendor source →

FloQast experienced a minor incident on February 23, 2026 affecting Automate the Close - EMEA and Automate the Close - APAC and 1 more component, lasting 36m. The incident has been resolved; the full update timeline is below.

Started
Feb 23, 2026, 03:06 PM UTC
Resolved
Feb 23, 2026, 03:42 PM UTC
Duration
36m
Detected by Pingoru
Feb 23, 2026, 03:06 PM UTC

Affected components

Automate the Close - EMEAAutomate the Close - APACAutomate the Close - US

Update timeline

  1. investigating Feb 23, 2026, 03:06 PM UTC

    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.

  2. resolved Feb 23, 2026, 04:09 PM UTC

    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).