See why an agent run failed, and fix it on the spot

Highlight

See why an agent run failed, and fix it on the spot. When you hand work to an automated agent, the worst thing it can report back is nothing. A run that ends in a bare "failed" leaves you guessing whether a provider timed out for a moment or the agent was pointed at the wrong thing. This week, Nash Agent tells you what happened.

• A plain-language reason on every failed run. A failed run now shows what went wrong, in plain language, along with a suggested fix, in the run history and when you hover a failed run. It applies to past failures too, so a run that failed last week explains itself now. That's usually enough to tell a transient hiccup from a misconfigured trigger at a glance.
• Re-run on demand. A Run now button in the agent's header starts a fresh run immediately. Fix the setup, run it again, and confirm the agent is healthy without waiting for its next scheduled run.

Read more in Scheduling and execution.

New & improved

Nash Agent

• Run history separates an agent's automated runs from your chat sessions with it, so its run count, activity sparkline, and status badges reflect the work it did on its own.
• Reorder the fields in a custom agent's structured output by dragging them into the order you want.
• Set up a results destination, email or Slack, without leaving the agent editor, see the exact recipients each destination resolves to, and open a finished agent straight from its confirmation card.
• Nash Agent chat answers are formatted for easier reading, and entity references render as clickable chips instead of plain text.

Platform API

• Set a zone's geographic boundary through the API: Create a zone (POST /v1/zones) and Update a zone (PATCH /v1/zones/{id}) now accept a polygon field. See Zones.
• Nash now supports Spain as a delivery country, with euro pricing and local address handling.

Integrations

• Australia Post senders that print their own labels can skip Nash label creation, so merchant-allocated shipments manifest without a duplicate-label error. *(Opt-in.)*

Portal

• The My Fleet settings page is redesigned with search, a category sidebar, and grouped setting cards, so a long list of fleet settings is faster to navigate.
• The Activities view recognizes dispatch-and-manifest runs and opens a results drawer with per-order status and the manifest PDFs.

Fleet

• The Execute route table shows each route's current stop status, for example, "drop-off en route", and new Route Status and Stop Status filters narrow the table to what you're looking for. (The route label "In Transit" is now "In Progress.")
• Download the routes you're viewing on the Execute page as a CSV.
• Notes a driver adds to a stop now appear in the Portal, in the route's stop list and the driver details card.
• Select routes on the Orders → Routes tab to dispatch, archive, optimize, or create them in bulk.
• On pickup and return runs, the driver app can show per-item counts, picked against ordered, with failed items kept out of the completion total, and mark an item "package not found" so the stop resolves as missing without creating a return. *(Opt-in.)*

Fixes

Nash Agent

• Scheduled report agents that do heavy, high-volume work no longer time out before they finish, and a report that used to arrive blank now carries the agent's findings, with the notification showing the agent's complete written report, tables included, rather than a one-line summary.
• A webhook-triggered agent runs when its event fires, and the raw webhook payload, including Zapier's format, is passed into the agent's prompt.
• Turning an agent off reliably stops it, including agents started by an alert, a webhook, or a file upload.
• Creating an agent by describing it now keeps an email recipient you name in the same request instead of dropping it.
• Nash Agent chat no longer repeats a mid-run follow-up, and rich text you paste keeps its formatting.
• When saving a custom agent fails, the message explains why, for example, that an event-triggered agent needs at least one trigger.
• When the Nash Agent voice agent handles a call about an order that was automatically reassigned to a new provider, it works from the live delivery attempt, so the status it reports and the reschedule it makes are for the active delivery, not a superseded one.

Integrations

• Purolator shipments with longer drop-off instructions are no longer rejected.
• FULFLLD deliveries show a live, updating drop-off ETA instead of a frozen one.
• Addison Lee accepts scheduled orders whose pickup is near-term instead of rejecting them.
• Medzoomer proof-of-delivery photos now appear on the delivery.
• GoShare deliveries move to en route when the driver sets off, not only once they reach the pickup.

Orchestration

• Deliveries to UK, Canadian, and Dutch postcodes entered without a space are no longer wrongly rejected as out of area.
• Stale, unaccepted driver offers expire and re-dispatch instead of leaving a delivery stuck without a driver.
• Merchants reliably receive the sent-to-provider and manifested webhooks on large batched dispatches.

Fleet

• The live-tracking map keeps following the driver after a batch stop is completed, instead of freezing at the first drop.
• The delivery timeline no longer shows each barcode scan twice.
• Editing a driver group, adding or removing drivers, no longer silently reverts your first change.
• Completed and canceled routes no longer offer a provider-reassign action that always failed.
• A route that ends with every stop failed or returned now shows as complete in the activity feed, and a returned delivery emits its full return sequence, return in progress, arrived, returned, even when no arrival was scanned.