Unable to use the same HumanWorkflow within textract for more than 1 file/call

0

I created the private team from the Amazon SageMaker console for labeling tasks followed by the creation of the human review workflow, which I later integrated with the Amazon Textract for Key-Value pair extraction.

While I called the analyze_document (along with HumanLoop configuration) to extract key-value pairs for the first time it worked as expected and I was able to see the Job in the labeling project console. However, when I called it again (irrespective of the same or different file) the HumanLoop started giving the below error.

"[ERROR] InvalidParameterException: An error occurred (InvalidParameterException) when calling the AnalyzeDocument operation: HumanLoop 'textractworkflow1' already exists and it is associated with a different InputContent. Please use a new HumanLoopName and try your request again."

Do we have to create a new Human Review Loop each time we trigger analyze_document with another file?

2 Risposte
1
Risposta accettata

I think you are using the same human loop name for multiple tasks and that is causing this issue. You have to make sure that within the HumanLoopConfig configuration, the HumanLoopName should be unique for each task. You can also refer to this video

con risposta 2 anni fa
1

Hello,

I'm from the AWS Textract team. Thanks for using Textract.

Most likely as per the details of the exception mentioned suggests there could be a need of using a new HumanLoopName. I believe someone from sageMaker team will shortly respond to this.

However to check if it is due to Textract calls, could you please help us out with the following questions:

  1. Could you please share the entire stack trace of the exception ?
  2. Is this exception being thrown at the time Textract is called ? If yes, could you check and compare the i/p parameters passed at the initial time when it passes and the next call when it fails ? Also please share the i/p parameters for both.

Thanks,

Nitish

con risposta 2 anni fa
  • Thanks for the response Nitish, I was passing the same humanloopname and it was problem. It is resolved now.

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande