Assignment rules now cover thirty-nine modules, and know what to do when everybody is full

There is a Run it now button and it works whatever the schedule says. The first thing anybody wants after setting this up is to see it act on what is already waiting. It reports what it did: how many it looked at, how many moved, and how many still had nowhere to go.

On a schedule it can come round every minute, every two, every five, twice a day or once a day, and the two day-scale ones can be pinned to a time, and a daily one to a day of the week. A run that arrives late still runs, so a restart over the moment it was due does not skip it.

It touches the overflow and nothing else, deliberately. A sweep that re-ran the rules across a whole module would fight every reassignment anybody made by hand, on every tick, and no screen would explain why the owner kept changing.

No. Nothing was reassigned, no existing rule changed behaviour, and no record gained an owner it did not have. The new modules have no rules until somebody writes one.

Some modules are deliberately still out, and it is worth saying which: warehouses, work centres, operations, job cards, employees, item categories, price lists, ledger accounts, the billing catalogue and the quality templates. Those are places, steps and rows you define once, not work a person answers for.