Resolved -
The fix for this incident has finished deploying. A full RCA will be shared in this posting as soon as it is available.
May 7, 16:18 PDT
Monitoring -
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.
May 7, 11:23 PDT
Update -
The fix is currently being applied in parallel to all FloQast environments. We expect the full resolution to be in place very soon.
May 7, 09:32 PDT
Identified -
The issue has been identified and a fix is being implemented.
May 7, 09:01 PDT
Investigating -
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
May 7, 07:28 PDT