Dynamics 365 Business Central: debugging agent sessions.
The 2026 release wave 1 (runtime 17.0) of AL Language extension adds the ability to debug agent sessions directly from Visual Studio Code. Developers can attach to agent sessions running on cloud sandboxes or on-premise servers using new launch configurations and can inspect what agents are doing by connecting via user security ID or session ID.
post Stefano Demiliani
"With this 17.x release it's possible to attach to agent sessions and debug the AL code they are executing."
Key points
- AL Language extension runtime 17.0 introduces debugging support for agent sessions in Business Central
- New client type Agent has been added along with two launch configurations for cloud and on-premise debugging
- Developers can attach to specific agent sessions using security ID or sessionId parameter
- Snapshot debugging stops at the next identified agent session for inspection and monitoring
Quotes
- “With this 17.x release it’s possible to attach to agent sessions and debug the AL code they are executing.” (This is the core capability introduced: developers can now actively debug agent code execution, which was not possible before.)
- “You can also use the sessionId parameter to connect to the specific agent session.” (Shows the granular control available: developers can target exact agent sessions rather than just the next one encountered.)
Context
- Features: agent session debugging, launch configurations, snapshot debugging, client type Agent
- Versions: 2026 release wave 1, runtime 17.0
Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.