RealTime Service - Known issues and Limitations

Missing heartbeat from Exchange Online

• In some on‑premises deployments of the RealTime Service, the service does not receive the expected heartbeat updates from Exchange Online. This can result in delayed or missing reservations in Resource Central, Exchange Central and WebTeam Central.
• This issue is not caused by Add‑On Products or the RealTime Service itself.
• The communication takes place between Microsoft 365 (Exchange Online) and the customer’s own infrastructure, such as firewalls, proxies, or network security devices.
  In these setups, the heartbeat traffic may be interrupted, filtered, or blocked before it reaches the RealTime Service.
• Because this happens outside our platform, we do not have visibility into the root cause and cannot resolve it directly.

Status: External dependency. The issue is related to communication between Microsoft 365 and the customer’s infrastructure.
A temporary workaround may be available, see customer action.
A permanent resolution will be to replace the RealTime Service with the new OfficePlace Connect.

Customer Action: For more details and possible workarounds, see: Missing heartbeat from Exchange Online

Applies to: RealTime Service (on‑premises deployments only) and underlaying system using RealTime Service, like Resource Central, WebTeam Central and Exchange Central

Last Updated: 29. May 2026

Permissions - Deleted Groups changes are not return (On-Premise)

• Using Resource Central permissions with groups on On-premise environments, Push notifications from Active Directory does not send notifications when deleting a group. 
• This will result in wrong permission settings on Resources in Resource Finder

Status: Analyzing for alternative solution

Workaround: Set up periodical Full Sync in RealTime Service to synchronize the groups correctly

Applies to: RealTime Service and underlaying system using RealTime Service permission functions like Resource Central

Last Updated: 2. Apr 2025