Our team investigated the incident and determined that some of the recurring automated tuning operations performed by the PostgreSQL database platform created a bottleneck in the LiquidPlanner operating environment. Requests backed up and some users experienced slow operations and errors.
We've since added additional database I/O capacity and adjusted the automated tuning operations to prevent this issue in the future.
Thanks for your continuing support and patience.