Most error messages in DivePilot name the problem, for example "This trip is fully booked". A few general ones do not. This page explains those, and the screens that look empty or broken when something failed in the background.
Why some messages are in English
A message DivePilot knows is shown in your language. A message it does not know comes straight from the server in English, whatever language you use. Either way, the action usually did not go through. Reload and check before you repeat it, because a change can still be saved when only the answer got lost.
General messages
| Message | What it means | What to do |
|---|---|---|
| "Cannot reach the server. Check your connection and try again." | No answer came back at all: your connection dropped, or a firewall blocks DivePilot | Check your connection and try again |
| "Something went wrong" | No usable answer came back: DivePilot is restarting for an update, too many requests came from your internet connection at once, or DivePilot took longer than a minute to answer | Wait a minute and reload. If it persists, check the status page. |
| "Internal server error" | Something unexpected failed on DivePilot's side. It also appears when an email could not be sent, for example on Resend invite or Resend email, even though the link itself may already exist. | Try once more. If it repeats, contact support with the time it happened. |
| "The system is busy right now - please try again in a moment" | DivePilot could not finish the change in time, usually because other changes to the same records were being saved at the same moment | Try again after a few seconds |
| "Too many attempts. Wait a moment and try again." | Too many attempts came from your internet connection | Wait a minute. Online booking, self-registration, waiver signing, saving a dive log, sign-up and new verification codes are limited per hour and may need up to an hour; setting a new password from a reset link may need up to 10 minutes. |
| "Resource already exists" | You tried to save something that already exists | Reload and look for the existing record |
| "This file is too large - the limit is … MB" | The upload is over its size limit | See An upload is refused |
Messages that point to a rule
A message such as "That seat is already taken" or "This staff member is already scheduled at that time" means DivePilot refused the change on purpose. The most common ones are quoted with their meaning in Messages that refuse an action.
A list is empty
When a list cannot load because the connection dropped, the server failed or too many requests were sent, DivePilot shows "Could not load this" with the reason and a Try again button, not the empty screen of a list with no records, such as "No customers yet" or "No bookings yet". Before assuming data is gone, press Try again or reload the page. Data is never deleted by a failed load.
Not found, or loading forever
- "Trip not found", "Booking not found" or "Customer not found" appear when the record was deleted or you are not allowed to see it. When the connection or the server failed, the page says "Could not load this" with Try again instead. Reload first, then see A menu item is missing or access is refused.
- "Course not found" with "It may have been deleted, or it is not one of the courses you can see." means the course could not be loaded: it was deleted, or it is not one you are allowed to see.
- A plain "Not Found" means the address itself does not exist in the app. Check the link, or start again from the sidebar.
The page crashed
A bare page saying "Something went wrong!" with a small "Show Error" button means the screen itself failed. Reload the page. If it happens again in the same place, press "Show Error", take a screenshot, and send it to support with what you clicked just before.
No offline warning
DivePilot shows no warning at the moment the connection drops; you find out at the next load or save. A list or page that cannot load says "Could not load this". A save made without signal either fails with "Cannot reach the server. Check your connection and try again." or keeps its button spinning and is sent once the connection comes back. On a weak connection a save can hang for a long time first, because DivePilot sets no time limit of its own. On a boat or at a dive site with weak signal, check that the change really appears before you move on.
Right after an update
When DivePilot has been updated while your tab was open, the tab may reload itself once when you move to another page. That is expected, and nothing you saved is lost. During the update itself, requests can fail for a short moment with "Something went wrong".
Still failing
If a message keeps coming back, see Contact support and check the system status for the status page and what to include when you write.
Did this not answer your question? Contact support