Live updates in DrillerDB depend on which app you use. When a signed-in session has a valid positive company id, the classic app receives pushed events from other sessions in the same company. The console checks for new notifications on a timer.
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: Check That Updates Arrive
- Sign in to DrillerDB on two devices or two browser windows, as users in the same company
- Make a change in one, such as saving a schedule entry
- Watch the other window for the update
- If it does not show, refresh the page
How Updates Reach You
| App | What happens |
|---|---|
| Console | The notification bell checks for new notifications every 30 seconds while the browser tab is visible. When you return to a tab that has been in the background, it checks again at once |
| Classic app | A live connection (WebSocket) pushes events from other sessions in your company, such as schedule updates, project status changes, notes, and notifications |
Live events are a performance improvement, not a replacement for manual refresh.
Connection Management in the Classic App
The classic app reconnects by itself when the live connection drops.
| Step | What Happens |
|---|---|
| 1. Disconnect detected | The app starts reconnecting |
| 2. Exponential backoff | Retry after 1 second, then 2, 4, 8 seconds, and so on, up to 30 seconds between tries |
| 3. After 10 tries | The app keeps trying once a minute until the connection returns |
| 4. Reconnected | Live updates resume. Refresh the page to catch any event you missed while offline |
Step-by-Step: Configure Notification Preferences
- Go to Settings > Notifications
- Turn the notification types you want on or off. Each switch saves as you change it
- Trigger a test event from another session
- Check that the bell count and list update
If live updates stop, refresh the page. Manual refresh always restores current server state.
Supported vs Not Documented Here
| Area | Current Documentation Position |
|---|---|
| Notification refresh | Console: every 30 seconds while the tab is visible. Classic app: pushed live |
| Schedule refresh | Pushed live in the classic app with a valid company context |
| User presence dots/availability UI | Not documented as supported |
| Guaranteed offline queue/sync for chat | Not documented as supported |
| Cross-company event delivery | Not 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
A Team Chat message did not send, or a conversation will not load?
- A message that fails to send stays in the conversation marked Failed to send -- tap to retry, and the page says why above the message box. "Message not sent: this team member can't receive Team Chat messages." means that person is no longer an active user of your company. "Message not sent. Try again." means the send failed for another reason; tap the message to retry.
- If the page cannot load the team list or a conversation, it says "Could not load team members" or "Could not load this conversation" and asks you to refresh. An empty conversation is only shown when there really are no messages.
- If it keeps failing after a refresh, check your connection and tell support.
Connection repeatedly disconnects?
- Check network stability
- Disable problematic browser extensions
- Clear browser cache and retry
Related Topics
- Real-Time Features - Company-context overview
- Live Notifications - Notification behavior
- Real-Time Schedule Updates - Scheduling sync behavior
- Connection Issues - Network troubleshooting