RocketChat / RocketChat/Rocket.Chat
Omnichannel/Livechat E-Mail doesn´t work
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
If the agents of the Omnichannel are offline, it should actually be possible to send an e-mail. This no longer works since version 6.7.0. After entering the date, an empty window appears and corresponding error messages appear in the log file (see below)
Steps to reproduce:
- Page where is the omnichannel/livechat window
- All Agents offline
- User give user information and klick send
- white window
- Log error messages occurs
Expected behavior:
Mail will be send at the support-mail-addressActual behavior:
white Window and no e-mail will be send
Server Setup Information:
- Version of Rocket.Chat Server:
- Operating System: 6.9.0
- Deployment Method:
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version: 14.21.3
- MongoDB Version: 5.0.26
Client Setup Information
- Desktop App or Browser Version: Google Chrome 124.0.6367.203 , Opera 109.0.5097.80
- Operating System: Windows 11
Additional context
The assignment to the agents and the corresponding departments does not work reliably either. The chats are often assigned to users without a department assignment, although these users may only be from a specific department.
Relevant logs:
In a continuous loop:
{"level":20,"time":"2024-06-11T08:07:37.120Z","pid":1672,"hostname":"rocketchat","name":"OmnichannelQueue","msg":"No more registered queues. Refreshing"}
{"level":20,"time":"2024-06-11T08:07:37.122Z","pid":1672,"hostname":"rocketchat","name":"OmnichannelQueue","msg":"Executing queue Public with timeout of 5000"}
{"level":20,"time":"2024-06-11T08:07:37.122Z","pid":1672,"hostname":"rocketchat","name":"OmnichannelQueue","msg":"Processing items for queue Public"}
{"level":20,"time":"2024-06-11T08:07:37.123Z","pid":1672,"hostname":"rocketchat","name":"OmnichannelQueue","msg":"No more items for queue Public"}
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
No source files or tests are named. Start by reproducing the Omnichannel/Livechat email flow with all agents offline and inspect the repeating OmnichannelQueue log entries; done means the offline contact form sends email successfully and the reported department assignment behavior is clarified or fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100