Problem: All encoding jobs are stuck in the "Scheduled" state and not being processed.

Solution: Increase vCPU quota for the encoders to allow scaling.

Encoding jobs can be stuck in a scheduled state for a number of reasons. The most common reason is that the number of jobs in the queue exceeds the concurrent job capacity of the encoding pool, meaning that jobs will have to wait for encoders to finish their current encoding task before picking up the next job.

However, if you find that no jobs are processing and all jobs are stuck in the "Scheduled" state, it may be the result of a mismatch between the number of encoders in the encoding pool and the vCPU quota for the encoder family. In this situation, the encoding service attempts to scale but finds that it doesn't have enough vCPU to spin up more encoders. The encoding pool then enters a "back off" state as it tries to resolve the discrepancy. Fortunately, this is easy to fix.

1. Open support ticket. Open a support ticket with Ravnur support. You can do this on the home page of the knowledge base website using the button on the top right corner.

2. Increase vCPU quota. Increase the quota for the VM family used in your encoding pool. If you don't know the VM family, Ravnur Support will tell you. The default encoder VM is F16s_v2 (Standard FSv2 Family, 16 vCPUs per VM). To scale to 20 concurrent jobs, make sure the Standard FSv2 Family quota in your region is at least 320 vCPUs. If your encoding pool uses F8als_v6 or F8als_v7, increase the Standard Falsv6 or Standard Falsv7 Family quota instead (8 vCPUs per VM, 160 vCPUs for 20 concurrent jobs). See How to add vCPU quota for your deployment.

3. Adjust encoding pool. Inform Ravnur Support when the quota request has been fulfilled. They will adjust the encoding pool to match the available vCPU. In about 30 minutes, the encoding pool will scale normally and process all jobs in the queue.