Lambda Errors and Runtime Errors Experienced Throughout the Application

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.

The fix is currently being applied in parallel to all FloQast environments. We expect the full resolution to be in place very soon.

The issue has been identified and a fix is being implemented.

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