jfang
September 22, 2024, 8:25pm
1
Describe the problem/error/question
When I try to run an AI Chat workflow, it says workflow could not be started. I think it has something to do with the AWS Bedrock authentication process.
I’ve tried different LLMs, OpenAI, and Groq works, but using AWS Bedrock results the error message.
What is the error message (if any)?
When I go into the Credentials section, AWS Bedrock has “Error fetching options from AWS Bedrock Chat Model”
Please share your workflow
Share the output returned by the last node
Information on your n8n setup
n8n version: 1.59.3
Database (default: SQLite): default
n8n EXECUTIONS_PROCESS setting (default: own, main): default
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on DigitalOcean
Operating system: Ubuntu 22.04 LTS
jfang
September 23, 2024, 5:00am
2
The latest n8n version where the AWS credential worked is version 1.58.0. It stopped working with version 1.59.0.
ria
September 26, 2024, 7:38am
3
Hi @jfang
Can you try to do a reconnect of the credentials? Which error are you getting?
jfang
September 27, 2024, 3:38pm
4
Hi @ria
Thanks for looking into to this. The connection tested successfully.
I’m now on n8n version 1.60.1 and the issue is persisting.
I have copied the text from the error and pasted it below.
Workflow could not be started
It was not possible to start workflow!
Problem running workflow
Cannot find module ‘@smithy /signature-v4’ Require stack: - /app/code/node_modules/@n8n /n8n-nodes-langchain/node_modules/@langchain /community/dist/chat_models/bedrock/web.cjs - /app/code/node_modules/@n8n /n8n-nodes-langchain/node_modules/@langchain /community/dist/chat_models/bedrock/index.cjs - /app/code/node_modules/@n8n /n8n-nodes-langchain/node_modules/@langchain /community/chat_models/bedrock.cjs - /app/code/node_modules/@n8n /n8n-nodes-langchain/dist/nodes/llms/LmChatAwsBedrock/LmChatAwsBedrock.node.js - /app/code/node_modules/n8n-core/dist/ClassLoader.js - /app/code/node_modules/n8n-core/dist/index.js - /app/code/node_modules/n8n/dist/config/schema.js - /app/code/node_modules/n8n/dist/config/index.js - /app/code/node_modules/n8n/dist/commands/audit.js - /app/code/node_modules/@oclif /core/lib/module-loader.js - /app/code/node_modules/@oclif /core/lib/help/index.js - /app/code/node_modules/@oclif /core/lib/errors/handle.js - /app/code/node_modules/@oclif /core/lib/errors/index.js - /app/code/node_modules/@oclif /core/lib/config/config.js - /app/code/node_modules/@oclif /core/lib/config/index.js - /app/code/node_modules/@oclif /core/lib/command.js - /app/code/node_modules/@oclif /core/lib/index.js
ria
October 2, 2024, 12:59pm
5
Hi @jfang
Sorry for the late reply. Could you please try version 1.61.0
It might got fixed with this update:
n8n-io:master
← n8n-io:update-langchain-0-3
opened 06:11AM - 25 Sep 24 UTC
## Summary
- Update Langchain and relevant dependencies to 0.3
- Remove [decom… issioned](https://ai.google.dev/palm_docs/deprecation) Google Palm nodes
- Remove direct AWS dependencies in favor of `@langchain/aws`, update Bedrock ChatModel and Embedding imports
- Include `lmChatAwsBedrock` and `lmChatGoogleGemini` in supported Tools agent nodes
## Review / Merge checklist
- [ ] PR title and summary are descriptive. ([conventions](../blob/master/.github/pull_request_title_conventions.md)) <!--
**Remember, the title automatically goes into the changelog.
Use `(no-changelog)` otherwise.**
-->
- [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up ticket created.
- [ ] Tests included. <!--
A bug is not considered fixed, unless a test is added to prevent it from happening again.
A feature is not complete without tests.
-->
- [ ] PR Labeled with `release/backport` (if the PR is an urgent fix that needs to be backported)
1 Like
jfang
October 4, 2024, 5:38pm
6
Hi @ria ,
Yes, it got fixed.
Hopefully future releases will be stablized for this.
Thank you,
Jeff
1 Like
system
Closed
October 11, 2024, 5:38pm
7
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.