2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a 2 ans
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
répondu il y a 2 ans
Thanks for the response Nitish, I was passing the same humanloopname and it was problem. It is resolved now.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
Thanks this is helpful!