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 exceed 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. Using the guidance in this article, How to vCPU Quota for Your Deployment, increase the quota for the VM family you are using in the encoding pool. If you don't know the VM family, Ravnur Support will tell you. The default encoder family and size is the F8s_v2. So if you want to be able to scale to 20 concurrent jobs, make sure the quota for the Standard FSv2 Family in your selected region is at least 160 vCPU.
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.