Delayed push notification delivery

[fxmanu]

Description:

I got an on-premise installation of Rocket.Chat and experiencing a delayed delivery of push notifications, sent through the official push notification proxy.

Push notifications on the Desktop App (Mac) is delivered immediately.

Steps to reproduce:

1. Send a message to someone
2. Wait about 2 Minutes until push notification is delivered

Expected behavior:

Receive push notifications immediately.

Actual behavior:

Push notifications are delivered delayed (approx. 2 Minutes; sometimes even longer).

Server Setup Information:

• Version of Rocket.Chat Server: 6.6.2
• Operating System: RedHat EL 9
• Deployment Method: npm
• Number of Running Instances: 1
• NodeJS Version: v14.21.3
• MongoDB Version: 6.0.11

Client Setup Information

• Operating System: iOS/Android
• We're using the official Rocket.Chat-Clients

Additional context

This issue is ongoing for years in our installation. We recently had a pro trial version and this didn't change the behaviour.

Relevant logs:

None

[XorZy]

I am having the same issue on a brand new snap deployment. Test notifications arrive instantly, whereas actual message notifications arrive very late, or sometime even never. This problem has been reported by all users on the server, each with different Android devices. I do not know if this is by design or it is a bug, but it is a major inconvenience as it makes Rocket Chat pretty much unusable for mobile users. Not sure if it is related but the documentation seems to mention a 120 second delay, with apparently no working way of disabling it.. (Actual delays are usually above 120 seconds though.).

[ethan3011]

Hi. is there any update? Thank you

[krenuser]

https://docs.rocket.chat/docs/push-notifications

Push notifications rules

Notifications are determined based on server settings, user preferences, and subscriptions. User status (online, away, offline)is no longer considered for email and mobile push notifications. Instead, these notifications go to a new queue following these rules:

• When the user is online, the notification is scheduled to be sent in 120 seconds
• When the user is away, the notification is scheduled to be sent in 120 seconds minus the amount of time he is away.
• When the user is offline, the notification is sent immediately.
• When the user reads a channel, all the notifications for that user are removed (clears the queue).
• When a notification is processed to be sent to a user, and there are other scheduled notifications:
  • All scheduled notifications for the user are now rescheduled to the current time.
  • The current notification goes back to the queue to be processed ordered by creation date.

[gigadani]

https://docs.rocket.chat/docs/push-notifications a copypaste of docs by @krenuser

So should this behavior of 120 second delays be overridable with the OVERWRITE_SETTING... environment variable or not?

[ethan3011]

Hi @kurspelli

I used the method below (in a Docker environment) and confirmed that I can receive Notification in real-time.

... environment: NOTIFICATIONS_SCHEDULE_DELAY_ONLINE: 1 NOTIFICATIONS_SCHEDULE_DELAY_AWAY: 1 NOTIFICATIONS_SCHEDULE_DELAY_OFFLINE: 1

...

[gigadani]

Hi @ethan3011

I have added the following to both compose.yml and .env files, without any success:

      OVERWRITE_SETTING_NOTIFICATIONS_SCHEDULE_DELAY_ONLINE: 1,
      OVERWRITE_SETTING_NOTIFICATIONS_SCHEDULE_DELAY_AWAY: 1,
      OVERWRITE_SETTING_NOTIFICATIONS_SCHEDULE_DELAY_OFFLINE: 1
      NOTIFICATIONS_SCHEDULE_DELAY_ONLINE: 1
      NOTIFICATIONS_SCHEDULE_DELAY_AWAY: 1
      NOTIFICATIONS_SCHEDULE_DELAY_OFFLINE: 1