# Scheduling failure: unable to schedule
**URL:**
**Author:**  [@Albaninho10](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAlbaninho10)%5C
**Post date:** [June 25, 2025, 2:19pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-unable-to-schedule%2F160642%2F1 "2025-06-25T14:19:57Z")
Hello,
I want to deploy my model but I always get this error after +/- 20 minutes of “deployment”:
Endpoint encountered an error.
You can try restarting it using the “retry” button above. Check [logs] for more details.
[Server message]Endpoint failed to start
Scheduling failure: unable to schedule
And in the logs I get this error:
`Error 502 while fetching logs for "mon-modele-bricks-hiv":`
Has this ever happened to anyone?
---
**Author:**  [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [June 25, 2025, 3:03pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-unable-to-schedule%2F160642%2F2 "2025-06-25T15:03:38Z")
Hi @Albaninho10 Thank you for reporting! We’re investigating now.
---
**Author:**  [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [June 26, 2025, 8:18pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-unable-to-schedule%2F160642%2F3 "2025-06-26T20:18:28Z")
Hi @Albaninho10 Thank you for waiting! This error message is related to availability of the GPU instance at the time of deployment - this can be resolved by selecting a different instance or region if possible.
We’ve added updating this error message so that it’s clearer on the roadmap, though there’s no ETA just yet. Please let us know if you have any feedback about Inference Endpoints - we’re all ears!
I also wanted to mention our [Model Catalog](/static-proxy?url=https%3A%2F%2Fendpoints.huggingface.co%2Fcatalog)%2C which has ready-to-deploy models that require no additional customization and deployment is verified by Hugging Face.
Let us know if you have other questions.
---
**Author:**  [@Pimpcat-AU](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FPimpcat-AU)%5C
**Post date:** [June 27, 2025, 12:31am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-unable-to-schedule%2F160642%2F4 "2025-06-27T00:31:07Z")
I’ve seen similar issues with deployment failures related to GPU availability. From what you’re describing, it seems like the GPU instance may not be available when the model tries to deploy, which causes the 502 error. One possible solution is to try selecting a different instance type or region during deployment to ensure that there are available GPU resources at the time of deployment. Also, double check if there’s any region specific resource limitation that might be causing the issue.
---
**Author:**  [@Albaninho10](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAlbaninho10)%5C
**Post date:** [June 27, 2025, 7:44am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-unable-to-schedule%2F160642%2F5 "2025-06-27T07:44:09Z")
Thanks for the reply, indeed by changing region and GPU the model is deployed correctly !
---
**Author:**  [@system](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fsystem)%5C
**Post date:** [June 27, 2025, 7:44pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fscheduling-failure-unable-to-schedule%2F160642%2F6 "2025-06-27T19:44:53Z")
Closed on June 27, 2025, 7:44pm UTC
This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.