RocketChat / RocketChat/Rocket.Chat
Outgoing WebHook Integration History: "Replay" does not submit the same data
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
We have used the "Replay" function in the Outgoing WebHook Integration History in the past to test/debug our web hooks. In the current version of Rocket.Chat this seems not to work anymore though. When we try to replay a "User created" event, it sends the user data for "rocket.cat" instead of the actual user that has been created.
Steps to reproduce:
- Create an Outgoing WebHook Integration with event trigger "User created".
- Trigger the event.
- Go to the Outgoing WebHook Integration History and click on "Replay".
Expected behavior:
The same data (with user that has been created) should be sent to the web hook. E.g.
{
"token": "xxxxxxxxx",
"bot": false,
"user_id": "000000000",
"user_name": "real.user",
"user": {
"_id": "000000000",
"type": "user",
"username": "real.user"
}
}
Actual behavior:
The user info for rocket.cat is sent to the web hook:
{
"token": "xxxxxxxxx",
"bot": true,
"timestamp": "2023-03-13T15:51:35.592Z",
"user_id": "rocket.cat",
"user_name": "rocket.cat",
"user": {
"_id": "rocket.cat",
"createdAt": "2023-03-13T15:51:35.592Z",
"avatarOrigin": "local",
"name": "Rocket.Cat",
"username": "rocket.cat",
"status": "online",
"statusDefault": "online",
"utcOffset": 0,
"active": true,
"type": "bot",
"_updatedAt": "2023-03-13T15:51:36.039Z",
"roles": [
"bot"
],
"avatarETag": null
}
}
Server Setup Information:
- Version of Rocket.Chat Server: 6.4.0
- Operating System: Linux
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Yes
- NodeJS Version: v14.21.3
- MongoDB Version: 5.0.21 / wiredTiger
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Outgoing WebHook Integration History "Replay" entry point and trace how the historical event data is loaded and submitted. Compare the replayed payload with the original "User created" event, then add or run coverage for replaying that event. Done means Replay sends the created user's data rather than rocket.cat's data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100