The Hub Management page allows administrators to fine-tune SignalR hubs for messaging and notifications without having to redeploy the site. Use it whenever you need to temporarily disable the hub, adjust the reconnect time during maintenance, or slow down aggressive reconnect behavior.
Open the panel
1. Log in with your administrator account.
2. Go to Control Workplace → Admin → Hub Management.
3. The page loads the current configuration from Azure Table Storage and automatically hydrates all controls.
Hub Availability
- Enable Message Hub and Enable Notification Hub to enable or disable the respective hubs. Disabled hubs prevent new SignalR connections from starting for this feature, while keeping the rest of the site online.
- The minimum interval between hub calls applies a per-user limit (in seconds). When setting a non-zero value, the browser waits the same amount of time between manual reconnection attempts initiated from the interface.
Connection behavior
Each hub receives its own connection profile. Values are checked before saving, so out-of-range numbers are automatically clamped.
Message Center
- **Initial delay (sec)** - Delay the first connection after the page loads.
- Reconnect backoff (sec) is a comma-separated schedule for automatic reconnect attempts (e.g. '5,15,30,60').
- Manual Retry Interval (sec) is the minimum delay before a user can request a reconnection.
Notification Hub
- Uses the same set of controls as the Message Hub, but applies to notification updates.
- Leave the reconnect field blank to return to the default schedule '[5,15,30,60]'.
Save Changes
1. Check all the values. Disabled hubs automatically gray out connection settings to let you know they're greyed out.
2. Select Save Hub Settings. Green toast confirms success; Red indicates validation or network issues.
3. Saved settings are written to the 'SignalRSettings' table, immediately invalidating caches. Clients commit the changes on the next reconnect cycle (usually within a few seconds).
Tips
- Use short delays (0-5 seconds) for production hubs to quickly restore real-time updates after a disruption.
- Temporarily increase the throttle value if unmanaged clients saturate hubs with spam when reconnecting.
- Remember that disabling the hub hides the associated real-time interface, but users can still get historical data through standard pages.