Closed mattfortech closed 5 years ago
@mattfortech Thank you for your quick action.
@PatrickFarley @anrothMSFT Hi team, please tell me if I am not reaching out the right person. This issue is effecting the customer experience, could you please help? Thanks a lot.
@mattfortech I am also having this issue when using the custom vision connector in Flow. The iteration has been published.
Error Code 404 { "Code": "NotFoundProjectDefaultIteration", "Message": "Project has no default iteration" }
Hello @YutongTie-MSFT , @PatrickFarley and @anrothMSFT , Does anyone know another way to flag an iteration as Default, if not through the Custom Vision portal? Or, can there be a way to fully qualify the API link so a default status isn't required? Any help would be greatly appreciated.
How long until the default iteration issue is fixed please? My code uses this feature and now its stuck on the old version of the model. If it's not fixed soon I'll have to rework it to specify the iteration and then remember to update it every time I publish a new iteration :-(
@robaker I have notified the PM about this urgent issue and am awaiting a response.
This recent update to the sample, removes evidence of a call that could have been used to make an iteration the default and add the iteration name to classification call. Removal of the default iteration, and addition of iteration name to all client code, is a deliberate breaking change.
I have the same issue, the endpoint has been changed from v2 to v3 and there is no default iteration, just published iteration. You have to specify the iteration when you call the service so it makes a lost of time to maintain client apps with the latest published model :(
@ToriParla I'm thinking I can set the expected iteration name, to LiveIteration for example, unpublish the old iteration then publish the new iteration with that same name, to avoid having to update the clients for each iteration. There's a brief window where there's no LiveIteration, which is kind of yucky.
Another breaking change. They abandoned the .NET SDK: Microsoft.Cognitive.CustomVision.Prediction and unlisted it from nuget. The replacement is almost identical, so I've got to revisit the code to put it back on a supported SDK. For no benefit.
We have 2 entirely separate feedback mechanisms in play here. Hell, why not? For the other way of having your valuable feedback urgently ignored, try this link: https://cognitive.uservoice.com/forums/598141-custom-vision-service/suggestions/37251376-default-iteration-feature-needed-to-be-back
@robaker , @ToriParla , The team has written up a guide on how to update your project to the recent SDK changes, including the removal of the default iteration feature - https://docs.microsoft.com/azure/cognitive-services/Custom-Vision-Service/update-application-to-3.0-sdk
@PatrickFarley Thanks Patrick (and team) - good to know.
@robaker @mattfortech We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.
Hello, I was requested (via @YutongTie-MSFT and @jimbobbennett) to start a new ticket for the Custom Vision/Default iteration issue. The documentation shows how to elect a model iteration as "default" - furthermore, the API will give a 404 error unless a model/iteration is marked as "default." Now for the bad news: The "make Default" option has been removed from the UI. I have interacted with Azure Tech support (they confirmed this bug). Has anyone else overcome the 404 error as a result of an inability to elect an iteration as Default? Thank you!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.