- Le plus récent
- Le plus de votes
- La plupart des commentaires
I was able to solve this error couple of days back. It actually meant that I was not able to trigger the underlying lambda in the agent. Reason, I suppose is due to some session mgmt issues. Managing the session id fixed this issue.
Hello,
The above error happens when the format of the model prediction could not be be parsed. The agent responds back with a final answer that it cannot respond to the user request, while the failure reason comes in trace.
We may need to get access to your agent schema and other code. So, to perform specific investigation into your issue and recommendations for next steps i request you to reach out to AWS Support [1] (Bedrock) along with your issue or use case in detail, and we would be happy to assist you further.
References: [1] Creating support cases and case management - https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a 2 ans
- demandé il y a 3 mois
- AWS OFFICIELA mis à jour il y a 5 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an