As described in the Sailor Logbook App manual, Upload subpage, an upload comprises all tracks in state RECORDED on your device. None of these are present at the Sailor Logbook Website in advance.
After an upload, tracks copied to the Website change state to UPLOADED on your device, and are kept in this frozen state: they cannot be changed in any way, and cannot be uploaded again. The only option is to delete one or more from your device (use the Tracklist for that).
Update to state UPLOADED happens when the Sailor Logbook Website confirms all uploaded tracks were processed.
Tracks on the App are transformed to cruises at the Website; cruises have no state, other then existing or not.
In principle, there is no limit to the volume of an upload: tracks for a whole year or more can theoretically be uploaded in one big chunk. On the other side, a small upload comprising one or only few tracks in a smaller chunk is an option, when uploading with regular intervals.
Usually there will be penty of time to complete uploads. But the Automatic harbor retrieval can be a time consuming issue, as the speed of this third party service cannot be guaranteed.
The important thing is, that an upload is done in one chunk, big or small, and the Sailor Logbook Website server must have enough time to complete the process to avoid a:
To illustrate what happens when an upload is too time consuming for the server to complete the process, consider this starting point, where all is fine:
Device Server u1 c1 u2 c2 r3 r4 r5
Hereafter an upload is begun, but doen't complete - resulting in this unfortunate situation:
Device Server u1 c1 u2 c2 r3 c3 r4 c4 r5
A server timeout is characterized by an upload subpage screen where nothing - except the spinning activity indicator - seems to happen for roughly 60 seconds, followed by a Communication errors screen:
You could simply retry the upload by tapping continue on your device. Cruises previously uploaded will be overwritten. Otherwise - and if retry also fails - continue below:
If you suspect a real timeout occurred - not just a communication problem caused by bad or no network connection - you should login to your account to see which cruises that exist there. In the example above, a 'c5' is missing. To repair begin by deleting the 'r3' and 'r4' cruises to reduce the volume for the next upload attempt:
Device Server u1 c1 u2 c2 c3 c4 r5
and then do an upload again to hopefully complete the server collection of cruises:
Device Server u1 c1 u2 c2 c3 c4 u5 c5
To fill in the gaps finally do a download - which should never experience timeouts - to end up with:
Device Server u1 c1 u2 c2 u3 c3 u4 c4 u5 c5
The simplest way is to limit the volume to be uploaded. You will probably have no problems if you don't accumulate more than one month of tracking before an upload. Maybe a whole season could be gathered. This depends on many factors, so you have to get your own feeling of how long it's safe to wait.
Of course, if you loose or damage your device, it's nice with backup, so uploading whenever practically possible is recommended.
The server logic examines if remaining time is becoming short because Automatic harbor retrieval is enabled, and if so temporarily suspends it to prioritize finishing the job:
If you ever experience a notification like the above, be aware that you may be close to a Server timeout mishap.
In the example above, the notification was provoked by setting a low threshold for when time is running short. In reality, a lot more than 77 tracks can be expected uploaded without problems.
The Automatic harbor retrieval checkbox - which was 'checked' / 'ON' in the example above - is one of the Event attribute checkboxes.
If the Automatic harbor retrieval feature was suspended, you can later supply missing harbors by:
Sailor Logbook Website manual - © Copyright 2018 CoaSoft ApS Denmark