Multiple signature fields in Azure Document Intelligence leading to internal server errors?

Question

Multiple signature fields in Azure Document Intelligence leading to internal server errors?

Mike Vilters 0

Hello, in my current document intelligence solution, I require two signature fields to be checked in the latest API 2024-11-30 V4.0 (GA). In theory this is possible but whenever I create a model with two signature fields it often leads to an internal server error. Sometimes however the model seem to work, but only when one of the two signature fields doesn't get found, and the other does. So that raises my question, is it only possible to have one signature field per neural model? Because multiple do seem to lead to a lot of internal server errors? Or is this somehow a problem with me? Thanks in advance!

Anonymous

2025-01-15T12:15:21.7933333+00:00
Hi Mike Vilters

Greetings & Welcome to the Microsoft Q&A forum! Thank you for sharing your query

The Azure AI Document Intelligence API version 2024-11-30 (GA) does support signature detection in custom models, including neural models. This means that theoretically, you can have multiple signature fields within a single model. can you please refer this

The internal server errors you are experiencing could stem from several factors, including model configuration issues or limitations in handling multiple signature fields simultaneously. While the API supports multiple signatures, it may not handle them effectively under certain conditions, leading to errors when both fields are present.

The behavior where the model works only when one signature field is not found suggests that there might be a conflict or resource limitation when both fields are being processed at the same time. This could indicate that the model to manage multiple signature detections concurrently.

I hope this helps you. Thank you.
Mike Vilters 0 Reputation points

2025-01-16T08:54:44+00:00

So is the only solution to it, having only one field present?
Anonymous

2025-01-20T04:28:46.92+00:00

Hi Mike Vilters,

Following up to see if the above response was helpful.
Anonymous

2025-01-21T05:29:04.0566667+00:00

Hi Mike Vilters,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

Anonymous

2025-01-15T12:15:21.7933333+00:00

Hi Mike Vilters

Greetings & Welcome to the Microsoft Q&A forum! Thank you for sharing your query

The Azure AI Document Intelligence API version 2024-11-30 (GA) does support signature detection in custom models, including neural models. This means that theoretically, you can have multiple signature fields within a single model. can you please refer this

The internal server errors you are experiencing could stem from several factors, including model configuration issues or limitations in handling multiple signature fields simultaneously. While the API supports multiple signatures, it may not handle them effectively under certain conditions, leading to errors when both fields are present.

The behavior where the model works only when one signature field is not found suggests that there might be a conflict or resource limitation when both fields are being processed at the same time. This could indicate that the model to manage multiple signature detections concurrently.

I hope this helps you. Thank you.
Mike Vilters 0 Reputation points

2025-01-16T08:54:44+00:00

So is the only solution to it, having only one field present?
Anonymous

2025-01-20T04:28:46.92+00:00

Hi Mike Vilters,

Following up to see if the above response was helpful.
Anonymous

2025-01-21T05:29:04.0566667+00:00

Hi Mike Vilters,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

Hi Mike Vilters,

sorry for delay

Using multiple signature fields in Azure Document Intelligence allows us to create a model that effectively meets our needs. We have successfully reproduced the scenario without any issues and are now in the process of training the model. can you please have a look once User's image

Ensure that all necessary permissions are granted.

Confirm which region you are using for the deployment.

Make sure that the multiple signature fields are clear and of high quality.

If you encounter any further issues, please retry the process, and feel free to reach out with any additional questions.

Thank you.

Share via

Multiple signature fields in Azure Document Intelligence leading to internal server errors?

1 answer

Your answer