Release notes
Choose who can edit each custom agent
Highlight
Choose who can edit each custom agent. An agent that writes the morning exceptions report or watches late deliveries for a whole team is shared work. Until now, anyone who could edit agents could change it, and the first sign of a well-meant tweak was a different report the next morning. Each custom agent now has Edit access, so its owner decides who can change it while everyone else keeps using it.
- Pick the editors. Edit access, at the top of the agent's page and the builder, offers Anyone in the org, the default, or Only specific people: the owner plus anyone you add with Add editors…. Org admins can always edit.
- Everyone else can still use it. People who aren't editors can still view, run, star, and duplicate the agent. Its settings, schedules, triggers, and version restores are locked for them, with a note saying who to ask.
- Chat follows the same rule. A change to the agent proposed in a Nash chat waits for someone with edit access to approve it.
Existing agents stay open to anyone who can edit agents until their owner restricts them. Agents your organization built are no longer labeled Personal. See Edit access.
New & improved
Nash Agent
- Ask Nash Agent what a custom agent found, such as "what did my fuel monitor flag yesterday?", and it answers from that agent's runs: the latest first, counts by status, each run's output with a link, and its open insights. It shows only runs you can see in the Portal.
- Tell Nash in chat to "add Saskia to the daily list" or remove someone, and only that recipient changes. Recipients added in the Portal, and Slack channels, are kept. You can also set the notification's title and message template from chat, and the approval card shows the old and new text.
- A custom agent's About card shows where its results go, in a Delivers to line with links to edit it and to Manage destinations. When you set up delivery in chat, Nash says up front that texting needs an SMS destination and links to it. Search the Portal for Destinations to open them. See Edit access.
- Attach screenshots and documents to a follow-up you send while Nash is still replying, and they arrive with it. Data files, such as CSV and XLSX, still wait for the reply to finish.
Portal
- In Execute, a route's Activity tab says how each exception ended: auto-resolved, closed when the route ended, expired, dismissed, or resolved by a named person and how, such as "resolved by Sam · Reassigned". It also shows when an exception was assigned, acknowledged, reopened, moved back to needs triage, or changed severity, and leaves out refreshes that changed nothing. Filters inside a group in Execute's filter panel are indented, so you can see where each group ends. (For organizations with Execute turned on.) See Routes.
- The Orders map's Layers control has a Zones layer that draws your organization's zones. Hover a zone for its name, and click it to isolate it. Route durations marked Times are out of date are no longer struck through; the clock icon still flags them. (For organizations with Routes turned on.) See Plan routes on the Orders map.
- In a delivery's Quotes box, a provider that didn't quote says why: Not in strategy, Not eligible with its reasons (such as "Outside this provider's coverage area"), or Unavailable with the provider's own message.
- On a contract, long provider names wrap with their IDs underneath, multi-select fields show three chips and a count you can open, and organization eligibility adds Select matching to add every search match at once.
Orchestration
- The workflow field Contract branches on the contract a delivery attempt was dispatched on, picked from your contracts, and keeps matching after the contract is edited. Notification triggers' Advanced options use the same contract picker. See Fields worth branching on.
- Courier Distance From Dropoff At Completion holds how far, in meters, the courier's last reported location was from the dropoff when the delivery completed. Use it to catch deliveries completed away from the door.
Platform API
- The Nash MCP server adds
list_configured_notification_triggers, which lists your alerts, their events and filters, and who they notify.find_orderfinds an order number read out with spaces, such as "G H 785 2045".create_ordertakesexternal_idandreference_id, andcreate_contract/update_contracttakeorder_service_factor, which lengthens a truck's time at each order stop. - When you swap the driver on a delivery that's already assigned, Nash records it in the status history and sends another
assigned_driverwebhook naming the new driver. (For organizations with Fleet turned on.)
Integrations
- Stuart deliveries that need an ID check for tobacco send Stuart
TOBACCOas a restricted item, alongsideALCOHOLwhen both apply, so the courier checks ID at the door.
Fixes
Portal
- Once a delivery's dispatch is canceled, its pickup and dropoff times, addresses, vehicle size, and delivery mode can be edited again, so you don't have to recreate the delivery and lose its external ID.
- A duplicated delivery keeps the original order's package metadata and tags, not just its items.
- The Deliveries Tags filter also matches the order's own tags, so deliveries dispatched on a route or batch no longer show no tags.
- Recipient groups saved without a description, including every group Nash Agent creates, can be edited and saved in Destinations and in trigger editors. The Driver Geolocation trigger's distance accepts decimals, such as 0.1.
- A contract saved before versions were tracked can be submitted again from its page.
- After an order is removed from a dispatched route, or a package moves off one, the remaining stops' planned times and distances are worked out again, and a driver break stays where it was. Route edits are timed with the traffic the route was planned on, and a route left empty drops its break. A route's planned cost uses its contract's rates, so the grid no longer shows a false gap against plan after re-optimizing a selection. (For organizations with Routes turned on.)
Nash Agent
- Action cards say what the action does, Review scrolls to the approval that's waiting, and Nash says why a follow-up wasn't queued. A long pasted follow-up sent mid-reply is queued instead of refused. Replies no longer stop short or go blank, and shared sessions get the star and ⋯ menu.
- A legacy custom agent's report run that promised files and delivered none retries once and is then flagged. A run whose summary says it failed or only partly finished is marked as needing attention, with the agent's reason.
Platform API
- An order sent with a one-line
pickupAddressordropoffAddressand coordinates keeps the coordinates as the address's pin, instead of landing in needs attention. - Saving a notification trigger without the parameters it needs is refused with an error, instead of saving a trigger that failed on every event.
Integrations
- An Uber refund that includes a return trip fee is recorded at the full amount Uber approved.
- A courier's Parking Location from Uber stays on the delivery after later location updates.
- Australia Post shipments booked late in the evening from Queensland are accepted, and items under 50 g are sent at gram precision instead of being refused.
Fleet
- Driver App 1.16, in the App Store and Google Play: on iPhone, the app no longer runs out of memory and closes after several HERE navigation sessions. On Android, lifting one finger while another is still on a scrolling list no longer closes the app. (1.16)