Exceptions at a glance

Note

This is a beta feature. Reach out to Nash if you'd like early access.

An exception is a flag on a live route that says something on that route needs attention: the driver left the depot late, the vehicle broke down, a customer wasn't home, a driver needs to refuel. Each exception carries a type (what happened), a severity from P0 to P3 (how urgent it is), a status (where your team is with it), and an assignee (who owns it). Exceptions live in Execute, the workspace for routes that are already out on the road, so the people watching live routes see the problem on the route it belongs to.

Most exceptions arrive on their own. Drivers report problems from the driver app, Nash raises some from route events, and workflows you build can raise your own. Anyone with access can also add one by hand when they hear about a problem first. Your team then works each one through the same three statuses — Needs Triage, Acknowledged, Resolved — until it's closed.

Exception handling is an add-on within Execute. Exceptions appear only when exception handling is on for your organization; if you use Execute and don't see an Exception column, reach out to Nash.

Where you see exceptions

• The Exception column in the Execute routes table shows each route's leading open exception — its type, status, and severity — with a count of any others. Hover it to preview every open exception on the route; a route with none shows an Add exception button instead.
• The Issues tab in the route panel lists the route's exceptions grouped by status, with a collapsed Resolved section underneath. Open any row to see its details and change it.
• The page header summarizes how many routes have open exceptions and how many are critical, and a row of severity filters narrows the table to Critical · P0, High · P1, Medium · P2, or Low · P3.
• The Assignee column shows who owns a route's open exceptions.

Some organizations also see KPI cards above the table that count routes with exceptions, open exceptions, and routes on track.

What you can do with exceptions

• Add an exception to a route — raise one by hand from a built-in type or one of your organization's own types, and let Nash set the severity or pick it yourself.
• Triage and resolve exceptions — acknowledge what you've seen, change severity, type, or status, resolve what's done, and clear a false alarm.
• Assign exceptions — hand a route's open exceptions to a teammate, one route at a time or several at once.
• Manage exception types — build your organization's own catalog of exception types, each with a default severity.

Together those cover an exception's working life: it's raised on a route, lands in the queue as Needs Triage, gets acknowledged and assigned to someone, and closes when that person resolves it — or on its own when the route ends and nobody had taken it.

Learn how it works

The task pages above tell you what to click. For the mechanics behind them — every source that raises an exception, how Nash decides an automatic severity, why assignment covers the whole route, and which exceptions close by themselves when a route ends — see How exceptions work.

For a lookup while you're working the queue, see the Exception types and severity reference: every built-in type, what raises it, its default severity, and what each severity and status label means.

Nash dispatches routes to providers and fleets; they run the deliveries. An exception is how a problem on one of those routes reaches your team, so someone can decide what to do about it.