Bedrock throws error on forking a conversation

[aryansaurav]

What happened?

I forked a conversation using the fork button above the text input box.
I was using AWS bedrock Claude3.5 v1 model for this ongoing conversation.

The fork was successful but chatting in the new forked conversation throws error. In the docker container logs, I see this error

2024-11-26 16:27:10 error: [handleAbortError] AI response error; aborting request: A conversation must start with a user message. Try again with a conversation that starts with a user message.
2024-11-26 16:27:16 error: [api/server/controllers/agents/client.js #sendCompletion] Unhandled error type A conversation must start with a user message. Try again with a conversation that starts with a user mess

It's an issue only with bedrock. It works if I select OpenAI model in the forked conversation.

Steps to Reproduce

1. start a new conversation with aws bedrock Claude 3.5 v1 model
2. fork the conversation, choosing visible messages only option
3. chat with the new forked conversation

What browsers are you seeing the problem on?

Safari

Relevant log output

2024-11-26 16:27:10 error: [handleAbortError] AI response error; aborting request: A conversation must start with a user message. Try again with a conversation that starts with a user message.
2024-11-26 16:27:16 error: [api/server/controllers/agents/client.js #sendCompletion] Unhandled error type A conversation must start with a user message. Try again with a conversation that starts with a user mess

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Try forking at a point that starts with a user message. It's a provider limitation because OpenAI does support the assistant role as the first message type, but Bedrock does not. I prefer to leave the error because this would not occlude the fact that the context is limited in some way other than the context window.