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

Omnichannel/Sessions chat closed not working #18259

Closed
rsgodinez opened this issue Jul 14, 2020 · 2 comments · Fixed by #18412
Closed

Omnichannel/Sessions chat closed not working #18259

rsgodinez opened this issue Jul 14, 2020 · 2 comments · Fixed by #18412
Assignees
Milestone

Comments

@rsgodinez
Copy link

Description:

Omnichannel/Sessions chat closed not working.
image

Steps to reproduce:

  1. In Admin/Omnichannel/Sessions, we have Livechat_agent_leave_action_timeout configured at 10 or 600 seconds.
  2. We start a Livechat conversation between Guest1 and Agent1 (bot).
  3. Guest1 closes Livechat (closes browser) so the conversation remains open.
  4. We force a logout-login in Agent1, expecting that after 10 or 600 seconds, the conversation closes.

Expected behavior:

After 10 or 600 seconds, Agent1 closes the conversation, so in Omnichannel/Chat History we will see:

image

Actual behavior:

Expected behavior was working until Rocket.Chat 3.3.3. Since Rocket.Chat 3.4.0, nothing happens. The conversation reamains open:

image

Server Setup Information:

  • Version of Rocket.Chat Server: 3.4.2
  • Operating System: Ubuntu 18.04
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: true
  • NodeJS Version: 12.16.1
  • MongoDB Version: 4.0.13

Client Setup Information

  • Desktop App or Browser Version: Chrome 83.0.4103.116
  • Operating System: Windows 10

Additional context

As I mentioned before, this issue happens with 3.4.0, 3.4.1 and 3.4.2. We still have another server with 3.3.3 where we still have the expected behavior.

We also think that maybe this could be something similar to another issue #18132 which started in 3.4.0 but was resolved in 3.4.1.

Relevant logs:

N/A

@renatobecker renatobecker self-assigned this Jul 15, 2020
@renatobecker
Copy link
Contributor

@rsgodinez thanks for reporting this issue.
I'll look into this case ASAP.

Thanks.

@dennishenry
Copy link

Is there any update on this? We're having the same issue on our instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants