Offline and sync

Backstage, coverage is poor. runorder lets you clock in and out, submit your week and mark notifications read anyway: the change is stored on your phone with the receipt “Queued — will send when you’re back online”, and goes on its own as soon as the network is back — even if you closed the tab in the meantime.

A banner at the top says how many changes are waiting: Offline — 2 changes queued without a connection, 2 changes waiting to send once the network is back but the sending is not done. Review opens the sync page. It is not in the menu; the banner is the way in.

The Sync page

Sync lists every queued change with the status Queued, Sending or Failed. With everything queued, the page says there is nothing to do — these send on their own. While sending, it counts “Sending 1 of 2…”.

A change becomes Failed when the server rejected it: the week was locked or already submitted, you were already clocked in, or there was no open shift to clock out of. The reason sits under the row. Retry sends it again, Discard deletes it, and Open takes you to the page the change concerned so you can see what is actually there. Retry all and Discard failed do the same for the whole list.

Already done is not a failure

If the phone loses the network right after the clock-in went through, the reply may have been lost on the way. When runorder gets “already clocked in” back on the retry, it counts the change as done and drops it from the queue.

Other changes — an event, a reservation, a form in Admin — are not queued. Without a connection you are told that changes will not be saved until you reconnect.