Some writes were refused
Not all sent" is the one warning that will not fix itself by waiting. Someone has to look.
2 min read
Not all sent. N writes from this device were refused and are waiting. Show this screen to whoever supports the system.
This is different from every other red banner, and it is the one to act on.
What it means
This machine reached the rest of the hospital perfectly well. It offered what it had done, and some of it was refused — not delayed, refused.
Waiting will not help. The machine will keep offering and it will keep being refused, because whatever is wrong with those records will still be wrong tomorrow.
Why it is shown so loudly
Because the alternative is worse. Before this warning existed, a machine in exactly this state showed green: it was syncing on time, so by the old measure it was healthy — while everything it recorded was being thrown away.
A machine that looks well while its work disappears is the most dangerous state the software can be in, because nobody looks. So refused writes turn the banner red and stay red. They do not age out.
What to do
1. Keep working, but tell somebody now. Work you do will be recorded. If the same fault affects it, it will join the queue.
2. Note the number. How many writes, and roughly when it started.
3. Show the screen to whoever supports the system. They will look at the refusal reason, which the machine holds. Common causes are a record in a shape the cloud does not accept — often a record loaded from an old register with something unusual in it — or a machine running a version of the software older than the cloud expects.
4. Do not reinstall the machine. Those writes are still on it and are the only copy. Reinstalling to "clear it" destroys them.
What is not lost
Nothing, provided the machine is left alone. Refused writes stay in the queue until they are accepted or explicitly resolved. When the cause is fixed, they go up and land normally.