Every change to a custom agent is kept, and you can put it back

Highlight

Every change to a custom agent is kept, and you can put it back. A custom agent that wrote a clean morning report for a month and then started missing things usually changed somewhere: someone reworded its instructions, swapped a connection, or moved its schedule. Until now the only record was the agent as it stands today. Each change now saves a numbered version on the agent's new History tab, so you can see what changed, who changed it, and undo it.

• Who changed what, and where. Each row reads like "Dana changed Instructions and Schedule", with where the change came from (the builder, a Nash chat, a document import, or the agent itself), how many runs used it, and when. The version your runs use is marked Live, and the builder's header shows it too, such as v7 Live.
• See exactly what changed. Open a version to see its changes, with the instructions shown as a line-by-line diff. Compare versions lines up any two, added, changed, and removed, files included. Nash chat's edit cards show instruction changes as a diff too, before you approve them.
• Put it back. Restore makes an earlier version's settings, schedules, connections, and files live again, and Undo last change steps back one. Skills aren't restored, and a connection that's since been deleted or turned off is skipped and named.

Anyone who can view an agent can read its History; restoring needs permission to edit agents. See Version history.

New & improved

Nash Agent

• Ask Nash Agent how a Portal page, setting, or permission works, or what changed recently, and it looks the answer up in these docs and links the page it used. Turning off Web access turns this off too. See Turn off web access.
• A webhook that starts a custom agent can say what it wants in a message field beside its payload. The response carries a result_url with the run's status and reply. Reusing an Idempotency-Key with a different body returns 409 instead of replaying the first run, and the run's transcript shows the body it received. See Start a run from your own system.
• Ask Nash in chat to add or change a custom agent's output fields. The confirmation card shows the fields before and after.

Portal

• The Routes grid counts trucks and drops. (For organizations with Routes turned on and Routing UI set to Grid.) See Plan routes on the Orders map.
• A truck that reloads at the depot is one row, marked 1 reload, and counts once. A route's stop count is its customer drops.
• Park routes, under Route Actions, sets routes aside while you plan the rest; bring them back from the Parked tab.
• Stops CSV downloads the stops of the ticked routes, with a column for each display field.
• Numeric display fields, such as pallets, get a total per route and for the day.
• A stop served in one of the order's other delivery windows shows that window marked Alt. and isn't counted late.
• Planned Complete is hidden by default. A column choice you've saved is kept.
• Map Display fields can show an order's package value, tip, weight, and dropoff instructions. (For organizations with Routes turned on.)
• Canceling a delivery shows what you're canceling, the provider and courier, and the Cancellation fee the provider estimates. Canceling a route lists its stops to choose from and doesn't show a fee estimate.
• Search for a driver by their External ID when you assign a delivery or a route. The ID shows beside each name, so two drivers called Sam are easy to tell apart.
• In Execute, a route's Activity tab keeps its exceptions after they're resolved: when each was raised, at what severity, and who resolved it, agents included. When filters hide every route, the empty state offers a button to undo each one, such as Clear search or Back to today. (For organizations with Execute turned on.)
• Custom roles can be given read on Contracts. A user limited to their own store locations needs it to see Fleet → Driver Groups. See Roles and access.

Engage

• Use short tracking links, under Customization → Tracking, gives new deliveries a short tracking link on Nash's tracking domain, with no custom domain needed. Links you've already sent keep working if you turn it off. Admins and Owners can change it. (Opt-in.) See Short tracking links.
• Progress Bar Color sets the tracking page's progress bar to your brand color. See Progress bar color.

Orchestration

• Send a webhook is a workflow action: give it an event title and a message, with variables, and it sends an event to your registered webhook endpoints. Only send once per order works on it. See Actions.
• Dispatch automation rules can test an order's item sizes: Max Item Length, Max Item Width, Max Item Height, Max Item Weight, and Items Volume (m³). Use them to send a parcel-sized order to a parcel strategy. See Dispatch automations.
• The workflow field Provider checks which provider has the delivery, picked from your providers, with In and Not In for several. Provider Delivery Id is now Provider Delivery Reference, and the Provider Name fields are marked Deprecated. Number fields show their unit, such as Items Volume (m³). See Fields worth branching on.

Platform API

• Create, update, and upsert orders with dropoffStoreLocationId to deliver to one of your store locations, the way pickupStoreLocationId works for pickups. dropoffExternalStoreLocationId fills the dropoff address from the store with that external ID. When you change an order's dropoff store, send its dropoff contact again.
• GET /v1/order/{id}/documents with load_data=true returns PDF and image data as base64. Text documents, such as ZPL labels, are unchanged.
• POST /v1/activities/optimization with contractIds and no scenarios runs one scenario across those contracts instead of returning 400.

Integrations

• Stores synced from Toast carry their Toast location name, such as Roti | Downtown, so a group's locations are easy to tell apart, and a sync for a large restaurant group imports every location.

Fleet

These Driver App changes reach every driver on version 1.15 without a store update.

• When a dispatcher or customer changes a stop's delivery instructions after the route has started, the driver gets a notification and the stop shows Updated in the route list. Opening the stop highlights the new instructions with the time they changed. (1.15)
• Drivers can open a route and read its stops before they check in. Until they do, it's read-only: the footer shows Check In, and each stop reads Check in to continue. (For organizations with a route check-in form.) (1.15)
• The New Camera Experience is on for every driver: the package list sits over a full-screen camera that boxes each barcode in view with its stop number. A driver who prefers the old scanner can turn it off in the app's settings. (1.15)

Fixes

Portal

• The Activity feed on a large route keeps the driver's events, such as calls and breaks, and each delivery's status changes. They used to stop after the route's first thousand events.
• A pickup row in a route's details no longer offers Remove or Move to another route.
• Moving a stop ahead of the pickup that carries its order is refused in the Portal, as Nash already refused it.
• A delivery status notification trigger created through the API can be edited and saved in the Portal.
• In Execute, times carry the time zone abbreviation in effect on their date, so an August stop reads EDT after the clocks change, and the route panel shows one time zone when the route's and yours match. Execute's triage card names routes that only a custom agent flagged. (For organizations with Execute turned on.)

Nash Agent

• An approval card comes back after a reconnect or when you return mid-reply, without a reload. Approving while the agent is still replying works, a message carrying only a file no longer blocks approvals in its chat, and thumbs-up and thumbs-down feedback saves.
• Press Enter to send dictated text. While it's listening, cancel to restore your earlier draft.
• A connection you delete, or an MCP server you remove, leaves your connector lists right away.

Fleet

• A route's return stop opens once every stop before it is done, even when earlier stops were failed out of order, so the driver can check in at the return's parking bay. With Enforce route sequence on, a canceled stop no longer blocks the stops after it.
• With Require arrival confirmation on, a driver who completes a stop offline is still asked to tap I've Arrived at the next one, so its arrival is recorded. (1.15)
• GS1-128 labels scan on Android with the new camera. (1.15)
• The Driver App's Earnings screen opens for date ranges that include a batch reassigned to another driver.