A change did not save

Wash Junkie saves to the device first and sends afterwards, so "did not save" is nearly always one of three things: the change is still waiting its turn, the server refused it and parked it for you, or it never entered the queue at all.

The chip in the bottom corner says which. Syncing 3 changes… means they are on their way. 3 changes need attention, in the warning colour, means at least one has stopped. No chip at all means nothing is outstanding on this device — what you are looking at is what the server holds.

What retries by itself

No signal, a slow moment at our end, a request that timed out. None of these need you. The queue keeps changes oldest first and sends them in the order you made them, and it tries again when the connection returns, when you come back to the window, and every 20 seconds regardless.

Running out of Wash Credit does not park queued work either. Anything already in the queue was accepted when you started it, so it sends and is charged — into an overdraft if it has to be. Wash Junkie would rather carry the overdraft than throw away laundry that has already been washed.

What parks and waits for you

A change the server will not accept however many times it arrives: an order that has since been removed, a field somebody else has changed, something the role you hold does not allow. It parks as needing attention, and the queue steps past it and keeps sending everything else — one stuck change never holds up the rest.

Open the chip and each parked change gives its own reason. Where there is no particular one to give, it says "We couldn't save this change. Try again."

One kind parks on a timer instead. A line item or a payment that has sat in the queue for more than 21 days is not sent at all, because at that age Wash Junkie can no longer be certain it would not be recorded twice. You get this:

This change was queued too long to sync safely — please check the order and re-enter it if it's still needed.

Two buttons sit under the list. Try again re-checks each parked change against what the server holds now, which resolves most of them without asking you anything — see Two people edited the same order. Discard drops it.

What never reached the queue

Two refusals happen before anything is stored, so there is nothing queued and nothing to retry: the area is paused, or the business has run out of Wash Credit. The form itself stays quiet and a notice appears in the corner naming the reason — retrying cannot work until somebody changes the thing it names. See An area is paused and Out of Wash Credit.

If the chip is empty and the change still is not there, the change reached the server and something else is going on — start with Working with no network.