An area is paused
A button has gone quiet, or it presses and nothing happens, and a notice arrives naming an area:
Drivers is paused — That didn't go through — the business owner paused this area. They can resume it in Settings → Billing & usage.
Nothing is broken. Somebody with the authority to do it turned that area off at this outlet. Hovering the control that would not press says the same thing in one line: "Drivers is paused. The owner can resume it in Settings → Billing & usage."
Some controls grey out ahead of the tap and some accept it and then refuse. The wording is identical either way, because it comes from the same place.
Pausing stops the work as well as the charge.
Paused, or out of credit?
Both refuse the work before anything is saved, both point at the same page, and neither leaves anything queued to re-send. They are not the same problem.
| An area is paused | Out of Wash Credit | |
|---|---|---|
| What the notice says | names one area | says the business has run out |
| How much stops | that area, at this outlet | all six areas, at every outlet |
| Why | an owner turned the switch off | the shared count cannot cover one more operation |
| The fix | the owner resumes the switch | the owner funds the balance |
Six areas carry a switch each: Orders, Customers, Drivers, Machines, Catalog and Staff. The switches are per outlet, so turning Drivers off at Mill Street leaves Drivers running everywhere else — while the Wash Credit behind them is shared by the whole business. That difference is the fastest way to tell the two apart: ring another outlet, and if they can do the same thing you cannot, it is a pause. See Out of Wash Credit.
Who can resume it
Only the owner. They are the only person who sees the switches, and the server refuses the change from anybody else — a teammate holding Staff & roles cannot move them either. Pausing an area is the full account of what the switch does before you ask for it back.
When the owner resumes it, dashboards already open on the floor pick it up on their own. Nobody has to sign out, and nobody has to go looking for the change.
What a pause does not stop
Reading, signing in, funding, resuming. And anything already queued on a device before the pause still lands when that device reconnects — a pause stops work being started, not work already done.