Manage exception types
Last updated: October 29, 2026
Nash comes with a set of built-in exception types, such as Late departure, Vehicle breakdown, and Customer not home. Your operation probably has problems of its own that don't fit those, like a store that was late to dispense or a dock that wasn't ready. Exception types let you name those problems once, so everyone raises and reports them the same way.
Once you create a type, it's available in three places:
- Add exception in Execute, under Your exception types, so your team can raise it by hand. See Add an exception to a route.
- Workflows, where the Create route flag action can raise it automatically. See the Workflow actions reference.
- Retyping in the exception inspector, so an exception raised under the wrong category can be moved to yours. See Triage and resolve exceptions.
Execute shows each type with its name and color, and the Trigger Type filter on the Execute page lists your types alongside the built-in ones.
Open the exception types page
Go to Settings ▸ Preferences, find the Exceptions card ("Define the exception types your workflows and agents can raise in Execute."), and select Manage exception types.
You can also get there from the Execute page's Table settings (select Manage exceptions), or by searching for Custom Exceptions in the command palette.
The Exception types page lists your organization's types with their Type key, Description, and Default severity, with a count of Custom types and Nash built-in types at the top. Below your own types, Nash built-in types lists the standard types. They're always available and read-only. The list also includes Unclassified, the fallback that catches any exception whose type can't be matched, so nothing is dropped.
Create a type
- Select New type.
- Fill in the form:
| Field | What to enter |
|---|---|
| Name | What your team calls it, as it should appear in Execute. Up to 200 characters. For example, Late pickup. |
| Type key | The permanent identifier workflows use to raise this type. It fills in from the name as you type (late_pickup); edit it if you want something different. Lowercase letters, numbers, and underscores, starting with a letter. It can't reuse a key that belongs to a built-in type. |
| Description | When your team should use this type. People raising an exception by hand see it on the form, so make it a one-line rule. For example, The driver left the store more than 15 minutes after planned departure. |
| Default severity | P0 to P3. Used when an exception of this type is raised without a severity: by a workflow that doesn't set one, or by a person who leaves Severity on Auto. Starts at P2. |
| Color | The dot shown next to the type's name in Execute. Red, orange, yellow, green, blue, purple, or gray. |
- Select Create type. You see "Exception type created," and the type is ready to raise straight away.
Important
The Type key can't be changed after you create the type. Workflows reference it, and it's stamped on every exception raised with the type. Settle on the key before you select Create type.
Pick default severities with care. Most exceptions of a type will carry its default, and the Execute queue sorts by severity, so a type defaulted to P0 will sit at the top of everyone's list. The Exception types and severity reference describes what each tier means.
Edit a type
Select a type in the list, or open its Actions menu and select Edit. You can change the Name, Description, Default severity, and Color; the Type key is locked. Select Save. You see "Exception type updated."
A new default severity applies to exceptions raised from then on. Exceptions already open keep the severity they were given.
Archive a type
Archive a type your team no longer uses. Open its Actions menu and select Archive, then confirm with Archive type. Once archived, the type:
- is hidden from every picker, so nobody can raise or retype to it;
- stays on the exceptions already raised with it, for history;
- can't be restored from this page.
To see archived types in the list, turn on Show archived.
If a workflow still uses the type, you can't archive it yet. The dialog reads Still in use and lists the workflows that reference it. Open each one, change or remove the action that raises the type, then archive again.
Who can manage exception types
Creating, editing, and archiving exception types needs write access to Organization Management on your role, set in Settings ▸ Members & Organization ▸ Roles. Access scoped to specific locations or driver groups doesn't qualify, even with that permission. If you don't see the Exceptions card on the Preferences page, you don't have this access; ask an admin in your organization. See Manage users and roles.