FloQast incident
500 error displays when AI generating a rule within Matching.
Resolved after 36 minutes, affecting Automate the Close - EMEA and Automate the Close - APAC and 1 more, on February 23, 2026.
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).
Affected components
Update timeline
- 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.
- resolved Feb 23, 2026, 03:42 PM UTC
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.
- 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).
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