Assign exceptions

Last updated: October 29, 2026

Assigning exceptions gives a route's problems an owner: the teammate who follows them through to a close. In Execute you assign exceptions by route, not one exception at a time. Whoever you assign owns every open exception on that route, and new exceptions raised on the route while it's assigned go to them too.

Exceptions appear in Execute only when exception handling is on for your organization. See the Exceptions overview.

How assignment works

It's route-wide. Assigning someone sets the assignee on all open exceptions on the route at once. The inspector says so under the field: "Changing the assignee applies to all open exceptions on this route."
New exceptions join it. An exception raised on a route whose open exceptions are already assigned picks up the same assignee.
It needs an open exception. A route with nothing open has nothing to assign. Its Assignee cell reads No exception, with the tooltip "Nothing to assign — route has no open exception."
The assignee is notified. Nash sends the person you assign a notification in the portal saying they've been assigned a route and how many open exceptions it has. Assigning yourself, or clearing the assignee, sends nothing.
Owned exceptions stay open when the route ends. When a route completes or is canceled, Nash closes open exceptions nobody has taken on. Assigned ones stay open for the assignee to resolve. See Triage and resolve exceptions.

The people you can assign are the members of your organization. The picker shows each person's name with their role underneath.

Assign one route from the table

In the Execute routes table, find the route's Assignee cell. If nobody owns the route's exceptions it shows a dashed Assign button; otherwise it shows the current assignee.
Select the cell. A picker opens under Assign to.
Search for the teammate ("Search users…") and select them.

The cell updates in place. To take the assignment off, open the cell again and select Clear assignee. If the change doesn't go through, you see "Failed to update assignee."

Assign one route from the inspector

When you're already working a route's exceptions, assign from there:

Open the route and go to the Issues tab, then select an exception to open the inspector.
Under Exception details, pick a teammate in Assignee, or pick Unassigned to clear it.
Select Save changes.

You can change the assignee in the same save as the status and severity. If you set the status to Resolved in that save too, the assignment is saved first, so it lands on all of the route's open exceptions before this one closes.

Assign many routes at once

To hand a batch of routes to one person, such as everything in one region at the start of a shift, assign from a selection:

In the routes table, tick the checkbox on each route you want, or tick the checkbox in the header to select every route on the page.
A bar appears with the number selected. Select Assign to and pick the teammate, or select Clear assignee to take the assignment off every selected route.

You see "Assigned 12 routes" (or "Unassigned …") when it's done.

Only routes with an open exception are updated. If your selection includes routes with nothing open, the bar tells you before you act, for example "14 selected · only 12 with an exception will update." If none of the selected routes has an open exception, the actions are unavailable.

If some routes fail, you see how many went through (for example "Assigned 10 of 12 routes"). The routes that failed stay selected, so you can retry them straight away.

Assigning from the bulk bar is the only bulk action on exceptions; status and severity are changed route by route.

Find what's assigned to you

The Exceptions filters on the Execute page include Assignee, with an Unassigned option for routes nobody owns yet. Filter to yourself to see your queue, or to Unassigned to find what still needs an owner. See Find routes in Execute, and Save and share Execute views to keep a "My exceptions" view one click away.

Who can assign exceptions

Assigning exceptions needs write access to Notification Settings on your role, set in Settings ▸ Members & Organization ▸ Roles. See Manage users and roles.