<@424021109164343316> <@780688794696286238> <@35...
# general-english
s
@slickVik @gzqq @malik We’ve identified these failures as call.in-progress.error-vapifault-worker-not-available errors caused by a sudden surge in requests that exhausted our worker pool. We’ve increased the minimum worker count and bolstered our auto-scaling settings to handle the load. It may take few minutes for the new workers to spin up, please retry your calls after few minutes and let me know if you still see any issues.