AzureML Data Labeling Project "Failed to submit one of the labels" when trying to convert a polygon to mask

Benedikt Schmitt 145 Reputation points
2024-05-08T06:40:21.1433333+00:00

I've set up a data labeling project for semantic segmentation. I want to start labeling my data but whenever I draw a polygon around part of the image and try to submit it, I get the following error:

"Failed to submit one of the labels

Service temporarily unavailable. Please try again later.

Trace ID: xyz Client Request ID: xyz"

-Tried closing and relaunching the AzureML-studio in hopes that that would fix it. It didn't.

-Tried waiting for a few hours but the error is still there.

-Tried labeling different data in another workspace that I've worked in previously. This worked so it could also be a permission-problem in the workspace

Azure Machine Learning
{count} votes

Answer accepted by question author
  1. santoshkc 15,600 Reputation points Microsoft External Staff Moderator
    2024-05-13T09:19:49.3633333+00:00

    Hi @Benedikt Schmitt,

    I'm glad to hear that your issue has been resolved. And thanks for sharing the solution, which might be beneficial to other community members reading this thread. Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

    Question: AzureML Data Labeling Project "Failed to submit one of the labels" when trying to convert a polygon to mask.
    Answer: The workspace was not automatically using my own permissions to access the storage and the workspace itself didn't have the necessary permissions to access the storage either. After giving the workspace the necessary permissions, it worked.

    If you encounter any issues in the future, don't hesitate to reach out to the community forum for assistance. Thank you.


    Do not forget to click Accept Answer and Yes for was this answer helpful.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Benedikt Schmitt 145 Reputation points
    2024-05-13T09:09:26.0766667+00:00

    To answer this, it was a problem with permissions.

    The workspace was not automatically using my own permissions to access the storage and the workspace itself didn't have the necessary permissions to access the storage either. After giving the workspace the necessary permissions, it worked.

    0 comments No comments

Your answer

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