You dispatched a route of twelve and got ten stops. The two missing ones were not lost: the system took them out on purpose, at the moment the dispatch was created, and it says why on each one. Here are the reasons, and what to do about each.
A location rule excluded it
Every address can carry service rules. An exclusion rule says "not on these days", "not in these hours" or "not in this weekly range", for some or all work types, and can be tied to the Holiday calendar. When the planned time of the dispatch falls inside such a rule, the address is removed and marked Excluded by rule, with the rule's name.
The rule is judged against the planned time when the dispatch is created, merged or edited, not when the driver arrives. A dispatch planned for 06:00 and driven at 09:00 is judged at 06:00.
A frequency limit is spent
A limit rule says "at most N times per day / week / month / season". The count is of planned dispatches in that period (every dispatch on which the address still has a live stop), not of work actually done. When the limit is reached, the next dispatch drops the address with the limit's name. Weeks run Monday to Sunday; "season" is your business's season range (and the rule is skipped when no season is configured or the date is outside it).
Too little snow fell
An address can say Only dispatch when snow exceeds a depth, on its Prices tab. When the dispatch's snow depth is below it, the address's plowing stops are removed, with Below minimum snow depth: 3 in (the threshold, in your unit) as the reason; salting-only work on the same address still goes out. Unlike the other reasons this one is re-checked when the depth on the open dispatch is edited: the stop comes back by itself once the new depth reaches the minimum, and an unworked stop is removed again when it drops below. A stop you restored by hand stays, either way, and a stop with work recorded is never taken off. It raises no error or warning, because a dry night is not a mistake. See Pricing by snow depth.
The owner switched off dispatching for you
A business that handed you an address can turn May dispatch my addresses off for your business. You still service the address when they dispatch it, but you cannot dispatch it yourself: it is greyed out in your pickers, and a route that includes it is dispatched without it, with a note. The switch follows the address down the chain: if the address was handed on to you by someone who is themselves blocked, you are blocked too.
The address is not active on that date
An address can be made inactive, now or from a date, and active again from a date. An address outside its active window on the planned date drops out of route and zone dispatching.
It is already on the dispatch
Adding addresses to a running dispatch skips the ones already there (Already dispatched in the picker) rather than creating a second stop. The same applies when two overlapping routes go out together: the shared address is one stop, carrying one pass per route, and each crew registers its own.
Restoring
Open the dispatch and click the removed stop.
- A stop a person removed comes back with Add to dispatch, and stays back: the next dispatch will not remove it again.
- A stop a rule removed asks you to confirm that you are overriding the rule. It is then serviced and invoiced normally, this once. It is not made immune; the next dispatch applies the rule again and, if it still matches, removes it again.
- A cancelled stop cannot be brought back. Dispatch the address afresh.
Seeing it coming
The dispatch picker already greys out what will be dropped and says why, and the summary before Confirm and dispatch lists the exclusions. The dispatch list adds a warning when a dispatch has Locations not in route or No business assigned, which are the other two ways an address ends up with nobody to do it.