Changes Could Not Be Saved
Symptom: A "Could not save changes" notification appears with "You can retry saving or discard your recent changes." Selecting the sync indicator in the header shows "Save Failed".
Solutions:
- Keep the page open and select Retry Save in the header. Discard & Reload drops the unsaved changes and loads the saved version instead.
- Check that the device has a stable connection to the practice network.
- If saving keeps failing, ask the person who manages Dermi Atlas Manager to check that the Real-Time Sync Server row on the Container Status card reads Healthy or Running, and to select Restart in the Atlas Control card if it does not.
Changes Made in Another Session
Symptom: A notification reports that a colleague or another open tab changed the same record.
- "Notes updated in another session". The entry notes were changed elsewhere while this session was saving, and the sync indicator shows "Save Conflict". Retry Save keeps the version on this device; Discard & Reload loads the newer one.
- "Appointment updated elsewhere". The appointment date from the other session has been kept. Check the date and change it again if needed.
- "Recent change not saved". The field returned to its previous value. Enter the change again; if it repeats, follow the steps under Changes Could Not Be Saved.
Offline or Loading Status
Symptom: The sync indicator shows "Offline" or stays on "Loading", and the header reads "Changes cannot be saved".
Solutions:
- Wi-Fi: Check that the Wi-Fi connection of the device is stable: move closer to the access point, and connect the host computer by cable.
- Firewall: Check that the real-time sync ports are allowed through the firewall of the host computer, as described in Firewall Configuration for Dermi Atlas Professional.
- VPN or proxy: Some VPNs and proxies block the real-time connection. Test on a direct connection to the practice network.
Atlas reconnects on its own. After a browser tab returns from the background or the device wakes from sleep, the indicator shows "Loading" briefly while the connection is restored.
Safari: Connection Blocked or Delayed
Symptom: Safari blocks or delays the connection to Atlas on the practice network.
Solutions:
- Allow Local Network Access when Safari asks for it.
- If access was denied before, turn it back on in the operating system. On iPhone or iPad, go to Settings => Privacy & Security => Local Network (or Settings => Apps => Safari). On a Mac, go to System Settings => Privacy & Security => Local Network.
- Use Chrome if Safari continues to block the connection.
"License expired" When Making a Change
Symptom: A change is refused with a "License expired" notification.
Solution: The license of the installation needs attention, for example because the host computer has been offline for seven days. See Troubleshooting Licensing and Subscription Issues.
Changes Appear Late on Other Devices
Symptom: Changes take longer than expected to appear on other devices.
Solutions:
- Edits appear in other sessions as they are made. Added and deleted records, such as images, zones, lesions, and sessions, as well as tag assignments and workspace membership changes, appear after a moment.
- Many people working at once, or a bulk operation, can slow updates.
For a session that ends during use, see Troubleshooting Account and Authentication Issues.
Related Articles
- Real-Time Synchronization Across Devices for how saving, presence, and reconnection behave in normal use
- Troubleshooting Network and Connectivity Issues for devices that cannot open Atlas at all