2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
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:
- Could you please share the entire stack trace of the exception ?
- 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.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
Thanks this is helpful!