# Uploaded Weights Not Working **URL:** \ **Category:** 🤝 Community Help\ **Created:** [October 8, 2025, 10:59am UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317 "2025-10-08T10:59:04Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![a1mm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/a1mm/32/6660_2.png) [@a1mm](https://discuss.roboflow.com/u/a1mm)\ **Post date:** [October 8, 2025, 10:59am UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/1 "2025-10-08T10:59:04Z")
I’ve fine tuned a Yolo11 l segmentation model using ultralytics version 8.3.40. When I upload the weights, I get an “Oops something went wrong, there might be issues with this model”. The imgsz when training was 1280 - would this cause an issue? I have also uploaded weights from an rf-detr-segmentation-preview model that was trained on robotflow (copied from one project to another), but it has been processing for 10+ hours so far. ---
**Author:** ![a1mm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/a1mm/32/6660_2.png) [@a1mm](https://discuss.roboflow.com/u/a1mm)\ **Post date:** [October 9, 2025, 4:48am UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/2 "2025-10-09T04:48:43Z")
I’ve tried many more times and still get the same error everytime. I have downgraded ultralytics one more version to 8.3.39. I have trained a model with all of the default parameters including img\_sz. I also changed the model type in the upload script to yolov11l-seg and yolo11l-seg. It always just gives the oops error. ---
**Author:** ![a1mm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/a1mm/32/6660_2.png) [@a1mm](https://discuss.roboflow.com/u/a1mm)\ **Post date:** [October 10, 2025, 8:14am UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/3 "2025-10-10T08:14:01Z")
I finally managed to get some models that work so far. I found the roboflow documentation and had to use: yolo task=detect mode=train model=yolo11l-seg.pt.. and even then, the cli seems to change task=segment automatically. before I was just running yolo train model=yolo11l-seg.pt… and the model always worked outside of roboflow, but would always give me the oops error in roboflow. I have no idea what is the difference in the model created between those commands though. ---
**Author:** ![Grzegorz](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/grzegorz/32/2877_2.png) [@Grzegorz](https://discuss.roboflow.com/u/Grzegorz)\ **Post date:** [October 13, 2025, 4:21pm UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/4 "2025-10-13T16:21:07Z")
Hi @a1mm , Are you uploading the model through the CLI (i.e. the `roboflow` command) or by directly hitting one of our POST endpoints? Thanks, Grzegorz ---
**Author:** ![a1mm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/a1mm/32/6660_2.png) [@a1mm](https://discuss.roboflow.com/u/a1mm)\ **Post date:** [October 13, 2025, 5:31pm UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/5 "2025-10-13T17:31:52Z")
I’m using the Python sdk ---
**Author:** ![Grzegorz](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/grzegorz/32/2877_2.png) [@Grzegorz](https://discuss.roboflow.com/u/Grzegorz)\ **Post date:** [October 14, 2025, 10:44am UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/6 "2025-10-14T10:44:44Z")
Thank you! Can you share the model ID you used when uploading that resulted in error? Thanks again, Grzegorz ---
**Author:** ![a1mm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/a1mm/32/6660_2.png) [@a1mm](https://discuss.roboflow.com/u/a1mm)\ **Post date:** [October 14, 2025, 8:42pm UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/7 "2025-10-14T20:42:37Z")
workspace.deploy\_model( model\_type=“yolo11l-seg”, model\_path=“./runs/segment/train6”, project\_ids=[“project-id”], model\_name=“yolo11l-seg” ) ---
**Author:** ![a1mm](https://yyz1.discourse-cdn.com/flex029/user_avatar/discuss.roboflow.com/a1mm/32/6660_2.png) [@a1mm](https://discuss.roboflow.com/u/a1mm)\ **Post date:** [October 14, 2025, 8:56pm UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/8 "2025-10-14T20:56:00Z")
The above is what i’m using. It works fine as long as I train using the command specified above, but not the way I have traditionally trained. Both models seem to work fine with ultralytics. Also, I had tried to upload some rf-detr weights (trained on roboflow in a different project). For model\_type, I used rf-detr-seg-preview. It has had the pending status for a week now. ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex029/uploads/roboflow1/original/1X/bb6edbfa56d0cf2ee603f061e9e09103502cc8cc.png) [@system](https://discuss.roboflow.com/u/system)\ **Post date:** [November 4, 2025, 8:56pm UTC](https://discuss.roboflow.com/t/uploaded-weights-not-working/11317/9 "2025-11-04T20:56:00Z")
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.