Skip to content

FIX : Threads messages fetching endpoint populated with unnecessary parameters. #1032

@Pratheek555

Description

@Pratheek555

Description:

When a user decides to convert a message to a thread for more discussions on the topic, messages are being saved which are sent in the thread but when tried to fetch the thread messages, backend throws an error which says that there were extra unnecessary parameters included in the API endpoint URL.

Steps to reproduce:

  1. Go to Embedded chat.
  2. Type a message and click on the threads option.
  3. Enter a message in the thread.
  4. Now try to go back and come back to this thread.
  5. When you check the network section, you can see the backend throws the error as a result of which the messages sent in the threads are not shown to the end user.

Expected behavior:

The threads messages should render correctly.

Actual behavior:

Currently we are hitting the right endpoint but with an extra query parameter which is causing the issue as show in the below snip shot.

Image
EmbeddedChat._.Simple.-.Simple.Storybook.-.Brave.2025-12-06.00-46-48.mp4

Endpoint being hit:

http://localhost:3000/api/v1/chat.getThreadMessages?roomId=GENERAL&tmid=ec_5ee90c109e3f4b03b
Based on the Rocket.chat code, there is no necessity of the roomId in the query parameter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions