Training Custom Vision model fails with unknown error

Niclas Schmidt 20 Reputation points
2025-04-17T13:06:44.8966667+00:00

When I try to train a custom model in Vision Studio it always fails with an error message stating: "Training failed unexpectedly. Please contact us for support and investigation."Error message

Things I have already tried without success:

  • using a different dataset
  • using different training images
  • retraining a model with data that has previously trained without issues
  • using a different resource
  • using a different server location
Azure AI Custom Vision
Azure AI Custom Vision
An Azure artificial intelligence service and end-to-end platform for applying computer vision to specific domains.
{count} votes

Accepted answer
  1. Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator
    2025-04-23T11:37:45.0033333+00:00

    Hi Niclas Schmidt

    Thank you for clarifying that you are using custom model feature from

    portal.vision.cognitive.azure.com

    Not from

    www.customvision.ai

    Wanted to quote this from custom model documentation

    This Customizing model feature is now deprecated. On March 31, 2025, Azure AI Image Analysis 4.0 Custom Image Classification, Custom Object Detection, and Product Recognition preview API will be retired. After this date, API calls to these services will fail.

    Screenshot (109)

    Please use custom vision portal only for model training.

    Sorry for the inconvenience.

    Thank you.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Alex Burlachenko 13,330 Reputation points Volunteer Moderator
    2025-05-27T09:05:59.6533333+00:00

    Hi Niclas Schmidt, in particular after you've attempted all the no-brainer solutions swapping out datasets, images, even resources and locations… come on, azure, work with us here

    alright, let's break that down. first of all, that error "Training failed unexpectedly" is a bit ambiguous, but it generally appears if the service encounters a hitch that it didn't anticipate. it could be a backend glitch, or possibly there's some kind of weird data formatting issue even if it used to work. lets see what you can do to try to resolve it

    check your image tags. at times, the custom vision service can become finicky if the tags are not uniform or are not present. ensure that each image has a tag, and the spelling of the tag is uniform throughout. microsoft's docs discuss that here.

    resize those images. if ur uploads are enormous (like 4K+ resolution), the service could slow down. see if scaling them down to under 6MB makes a difference. the docs are recommending keeping them between 256x256 to 1024x1024 pixels here.

    region does indeed matter. you mentioned you tested different locations, but make sure ur custom vision resource and ur storage (in case ur utilizing one of those) are in the same region. getting them mixed up can lead to silent fails.

    1. quota limits. Sneaky one if ur subscription crossed over into one of those obscure limits (e.g. api calls or training time), the service could just… give up. take a look at ur azure metrics to exclude that.

    occasional glitch. azure is big, but it's not perfect. the service just burps from time to time. wait sixty minutes, retry, and pray to the cloud gods

    So, hope that will help, at least i try to help

    Best regards,
    Alex
    P.S. If my answer help to you, please Accept my answer
    PPS That is my Answer and not a Comment
    https://ctrlaltdel.blog/
    
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.