Chat with us, powered by LiveChat
NewDrillerDB Enterprise SalesSee it

Real-Time Updates

Live notification and schedule-refresh behavior, including company-context limits

Real-time behavior in DrillerDB is company-context dependent. When a signed-in session has a valid positive company id, selected events can trigger faster notification and schedule refresh behavior between active sessions in the same company.

Live delivery requires a valid company context and an active network connection. If an event does not arrive, refresh the page to reload current server data.

Quick Start: Enable Real-Time Notifications

  1. Sign in to DrillerDB
  2. Open Settings > Notifications
  3. Enable the notification categories you want
  4. Open a second session and trigger a test change
  5. Confirm live behavior, or refresh manually if another session does not update

How Real-Time Updates Work

When enabled, the WebSocket connection can trigger:

  • Notification refresh events for in-app notifications
  • Schedule refresh triggers for active scheduling views
  • Automatic reconnect attempts after disconnects (up to 10 retries with backoff)

Live events are a performance improvement, not a replacement for manual refresh.

Connection Management

The WebSocket client includes automatic reconnect logic when enabled.

Connection Status Indicators

StatusDisplayUser Action
ConnectedLive updates activeNone needed
ReconnectingTemporary interruptionWait for auto-reconnect
DisconnectedNo live eventsRefresh after connectivity returns

Automatic Recovery Process

StepWhat Happens
1. Disconnect detectedClient starts reconnect logic
2. Exponential backoffRetry: 1s, 2s, 4s, 8s... (max 30s)
3. Retry limit reachedStops after 10 retries
4. Manual fallbackUser refreshes page to resync

Step-by-Step: Configure Notification Preferences

  1. Go to Settings > Notifications
  2. Enable/disable categories you want to receive
  3. Save settings
  4. Trigger a test event from another session
  5. Confirm notification count/list updates

If live updates stop, refresh the page. Manual refresh always restores current server state.

Supported vs Not Documented Here

AreaCurrent Documentation Position
Live notification refreshSupported with a valid company context
Live schedule refresh triggersSupported with a valid company context
User presence dots/availability UINot documented as supported
Guaranteed offline queue/sync for chatNot documented as supported
Cross-company event deliveryNot supported; sessions must share company context

Chat Behavior Note

Chat is available in DrillerDB, but this page does not assume WebSocket-backed chat delivery for all accounts. If message state appears stale, refresh the conversation.

Troubleshooting

No live updates at all?

  • Confirm both sessions have a valid company context
  • Check internet connectivity
  • Refresh active sessions

Schedule view looks stale?

  • Refresh Scheduling
  • Confirm the change actually saved
  • Verify both users are in the same company context

Connection repeatedly disconnects?

  • Check network stability
  • Disable problematic browser extensions
  • Clear browser cache and retry