Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]Chat continuity breaks when sending new message after AI response #639

Open
fjlana opened this issue Dec 10, 2024 · 6 comments
Open
Labels
needs-info Need more information such as reproduction step

Comments

@fjlana
Copy link

fjlana commented Dec 10, 2024

Description:
When interacting with Claude in Bedrock, the conversation flow is interrupted after receiving an AI response. Each new user message creates a new conversation instead of continuing the existing thread.

Steps to reproduce:

Start a new conversation with Claude
Send an initial message and receive Claude's response
Attempt to send a follow-up message
Observe that the new message starts a fresh conversation instead of continuing the previous one

Expected behavior:
The conversation should maintain continuity, allowing users to send multiple messages within the same chat thread after receiving responses from Claude.

Current behavior:
Each new user message after Claude's response creates a new conversation, losing the context and history of the previous interaction.

Impact:
This issue significantly impacts the user experience and the ability to maintain contextual conversations with the AI. Users cannot build upon previous exchanges or reference earlier parts of the conversation.

Environment:

Bedrock Claude chat: 2.3.0
Platform: Safary (ios) & Google Chrome (windows/linux)

Thank you

@statefb
Copy link
Contributor

statefb commented Dec 11, 2024

Thank you for reporting this behavior. This is actually working as designed. Please wait until the conversation title appears in the chat history before proceeding with your next message. This will ensure proper continuity of the conversation. Let our team consider UX improvement on another issue. thank you

@statefb statefb closed this as completed Dec 11, 2024
@statefb statefb reopened this Dec 11, 2024
@statefb statefb added the needs-info Need more information such as reproduction step label Dec 11, 2024
@fjlana fjlana closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2024
@fjlana
Copy link
Author

fjlana commented Dec 11, 2024

Hello,

Not working, I have tested as you said, sent a chat, wait until new conversation appears and this is the result:
image

image

Thank you

@fjlana fjlana reopened this Dec 11, 2024
@statefb
Copy link
Contributor

statefb commented Dec 11, 2024

Could you check cloudwatch logs for websocket handler and api handler?

@fjlana
Copy link
Author

fjlana commented Dec 12, 2024

Hello,

Here you have the data, it uses a different ID when sending the sencond message, thank you
image
image

@statefb
Copy link
Contributor

statefb commented Dec 16, 2024

Can you see any error messages on logs? Please check both websocket handler and api handler

@fjlana
Copy link
Author

fjlana commented Dec 16, 2024

Hello,

The problem seems to be this one
image

[INFO] 2024-12-12T10:28:34.498Z 6a5b7708-c7ea-4f5f-8e27-404aef48358b Received chat input: conversation_id='01JEX6KCQ5AHJQXYJ20NSG91G7' message=MessageInput(role='user', content=[TextContent(content_type='text', body='prueba 1')], model='claude-v3.5-sonnet-v2', parent_message_id='system', message_id=None) bot_id=None continue_generate=False
[INFO] 2024-12-12T10:28:35.145Z 6a5b7708-c7ea-4f5f-8e27-404aef48358b No conversation found with id: 01JEX6KCQ5AHJQXYJ20NSG91G7. Creating new conversation.

When creating the new conversation, the browser does not select the newly created conversation, so it generates a new convesation_id every time a message is sent. If I select the new conversation after it appears, doing click on it, it works properly.

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-info Need more information such as reproduction step
Projects
None yet
Development

No branches or pull requests

2 participants