Troubleshoot | The job takes an unusually long time to complete

Your job might be queuing because other jobs (launched by yourself or by other users on your space) are consuming all allowed resources. Other users in your account might be using some resources in your subscription’s quota, so your job might be queuing before starting. You can check your resource quotas to investigate.

Also, note that there might be a latency of up to two minutes for the job to start, as it may require additional resources. This may happen more often with larger configurations.