- Feature
- Debug recorded Business Central failures with an AI agent
- Availability
- Generally available (October 2026)
- Industry focus
- Road transport, freight forwarding and logistics
Transport and logistics companies connect Business Central to a web of other systems. Transport management platforms, telematics, customs portals, fuel cards and customer EDI all feed it. When something fails, it often fails only in production, only sometimes and only for certain users. Business Central 29.0 brings an AI agent into the hunt for those errors.
The industry challenge
A haulage or freight forwarding company might see errors like these:
- A job costing posting fails for one depot but not the others
- An integration from the transport management system errors on a few consignments each week
- A fuel surcharge calculation throws an error only for certain customers
These are the hardest errors to fix because developers can't easily reproduce them. Business Central has a snapshot debugger that can capture what happened in a real session. But setting it up correctly, waiting for the right session and collecting the snapshot takes skill and time. By the time it's ready, the user who hit the error has often moved on.
Meanwhile, invoices are delayed, costs aren't posted and operations staff build workarounds.
What Microsoft delivered in Business Central 29.0
Business Central 29.0 adds an AI-guided workflow on top of snapshot debugging. According to Microsoft:
- A developer describes the failing scenario to an AI agent.
- The agent sets up recording for the next matching Business Central session, or for a known session.
- It monitors the recording's status.
- It collects the completed snapshot so the developer can debug it offline.
Microsoft says this lets developers investigate intermittent or production-only AL failures without having to configure and run the snapshot debugger by hand. It also helps support teams capture the execution behind an error even when the affected session doesn't exist yet.
Where the value shows up
| Business area | Impact for a transport company |
|---|---|
| Time to fix | Faster capture of hard-to-reproduce errors |
| Billing and cash flow | Fewer delayed invoices caused by failed postings |
| Support capacity | Less specialist effort spent setting up debugging |
| Operational trust | Fewer workarounds built around unreliable processes |
| Partner collaboration | A clean snapshot gives the developer evidence, not guesses |
The real gain is in the gap between "we have a problem" and "we know why." In logistics, that gap is measured in delayed invoices and frustrated depot staff.
A worked scenario
Consider a regional haulier running eight depots (an illustrative example). Every few days, posting a job from its transport management integration fails for one depot with a vague error. The IT manager can't reproduce it in the sandbox.
The support developer describes the problem to the AI agent: job postings from depot six failing during the evening integration run. The agent sets up recording for the next matching session and monitors it. Two evenings later, the error happens again, and the agent collects the snapshot.
The developer steps through the snapshot offline the next morning. They find that depot six has a dimension value blocked in Business Central but still sent by the transport system. The fix is a data correction and a validation in the integration, made within a day.
Adoption considerations
- Agree who can trigger recordings. Snapshot debugging captures real data from real sessions, so restrict it to authorized support staff.
- Describe the scenario precisely. The better the description of the user, time, process and error, the more likely the agent captures the right session.
- Mind sensitive data. Snapshots may include customer and pricing data. Handle and store them carefully.
- Use it alongside telemetry. Telemetry tells you something went wrong. The snapshot tells you why.
- Close the loop. After fixing, add a test so the same failure can't return unnoticed.
The bottom line
Transport and logistics companies can't afford processes that fail at random, because every failed posting delays a bill or hides a cost. AI-assisted snapshot debugging in Business Central 29.0 makes the hardest errors easier to capture and fix. That's good news for IT teams, partners and the operations people who depend on the system every day.
If intermittent errors are eroding trust in your Business Central integrations, it's worth reviewing your support and debugging approach with an experienced adviser.
Source: Microsoft roadmap 573361