Repository navigation
Private Model took 12h to setup, isn't there a 10min limit ? #441
Description
Activity
Hi,
I have a few key questions regarding this issue that I’d really appreciate clarity on:
Why was the 10-minute timeout bypassed in this case? In other instances, I’ve seen the setup fail with the expected 600-second limit. This time, it ran for 12+ hours before failing — which seems like an orchestration bug or platform error. Can engineering retrieve and review the expired setup logs internally? These logs are now over 10 days old and no longer accessible to me, so I can’t troubleshoot from my side. Will these charges be reversed or credited, given that no usable result was produced? The setup ran for hours, failed, and produced no prediction output — resulting in high but unnecessary costs.I've also reached out to support but haven't heard back. Please escalate this — it’s important to get a resolution and avoid similar failures in the future.
Thanks,
Kanchana.
Hi,
One of my private models took 12+ hours to setup, twice. This incurred high costs for nothing.
I can see that the predict function was executed after 12h and failed.
I can not view the setup logs since this is 10 days old.
Is there a way to view older logs ?
Isn't there a 10min limit to setup the model ? I got this error sometimes
model container failed to boot and complete setup within 600 secondsbut this time it ran for 12 hours.I contacted the support but struggling to get a reply