Each question below is a problem operators actually hit, why it happens, and
what to do.
A job I created isn't on the calendar. Where did it go?
The board shows one day at a time, so check the date at the top first; the
job sits on its scheduled date. If the job was cancelled or skipped, it
is hidden by default. On a computer, open Tools and switch on
Cancelled; on a phone, use Show Cancelled in the menu. Skipped
recurring jobs come back with the same switch.
A job doesn't appear on the dispatch map.
The map places a job at its site's map location. A site whose address was
never found on the map has no location, so its jobs can't be drawn.
PortaPro retries those addresses on its own, but an address it couldn't
find waits until someone edits it. Open the site, correct the street
address (or drop a GPS pin), and save.
A recurring service job didn't generate.
Open Settings → Routing → Scheduled service generation and click
Preview run. The Last run line counts rows that were not yet due,
had no frequency, or sat on an inactive site. The usual causes:
service is due, 3 by default). A row that has never been serviced gets
its first visit one full interval from today.
On Call, Paused, Seasonal, Inactive, or closed).
See Recurring Service Jobs from the Rate Card.
A recurring job generated without a product on its line.
The rate-card row isn't linked to a catalog product. The job still lands,
but its line says "match to a catalog product to enable billing". Open the
customer's Rate Card and pick the product on that row.
I can't assign a particular person as the driver.
Driver pickers list drivers. An admin or dispatcher appears only when
Enable Tech View for Admin/Dispatch Staff is on (Team Management →
Staff Settings) and Tech View Access is turned on for that person in
their profile. Mechanics and shared truck logins are never listed.
A driver says they can't see their job.
A job shows in the driver app only once it is assigned to that driver.
Check the job's driver and date on the board. Recurring jobs land
Unassigned, so they reach no one until assigned. If the driver also
didn't get a notification, check that push is set up on their phone (see
The wizard won't go to the next step.
Each step names what's missing in red:
date", and for a delivery, "Pick the last rental day on the calendar, or
enter how many days to keep the units." A delivery with Long-Term Rental on
is refused here: long-term rentals are set up on the Rate Card.
continuing.", any quantity of 0, or a recurring service set to end by a
date with no date picked. A delivery with pickups needs units allocated
to the pickups.
Location and driver are optional at this point.
It says a unit is already booked.
Each unit can be on only one job for any given dates. "These units are
already booked for overlapping dates" names the units. Pick different units
or different dates.
A driver marked a stop as not completable and the job is still open.
That is on purpose. A service line marked unable keeps the job open, and it
shows as a missed stop under Needs attention with the driver's reason.
Reschedule it, skip the cycle (recurring jobs), or dismiss it. Completing
the job's other lines does not close it.
A stop is listed as missed but the driver says they did it.
A stop counts as missed while the job is still open after its day ends.
If the driver did the work but never marked it complete in the app, mark
the job complete and it leaves the list. Completed, cancelled and skipped
jobs are never listed. See [Missed Stops and
Rescheduling](/article/rescheduling-a-missed-stop).
"Skip this cycle" isn't on the menu, or it fails.
Only auto-scheduled recurring jobs can be skipped, and a completed job
can't be ("Completed jobs cannot be skipped."). Cancel a hand-made job
instead.
Route Plan left some stops out.
A stop needs an address or a GPS pin, must be scheduled on that day and
not be completed or cancelled. A job assigned to a driver who isn't working
that day is left out. When a stop can't fit (equipment, time window, shift
hours), Route Plan lists it with the reason; Plan anyway (skip unroutable
stops) leaves it in Unassigned. See
Planning and optimizing routes.