---
id: post/bertverbeek-nl/1263
type: post
title: Agents in Business Central – part 4 – troubleshooting
summary: This post explains how to troubleshoot Business Central agents when they don't behave as expected. It covers diagnostic tools like the Agent Consumption page and Agent Task Log, and identifies common pitfalls including unclear error messages, poorly written tooltips, excessive fields, and duplicate captions that confuse agents.
tier: community
language: en
tags:
  - agents
  - troubleshooting
  - diagnostics
  - error messages
  - agent design
  - consumption billing
system: copilot
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:56:44.042Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 234fa87eea91b285957e0741aba6a1749907096fb7f5cf1dc71ad6505e9b89c1
evidence:
  - kind: blog
    url: https://www.bertverbeek.nl/blog/2026/02/20/agents-in-business-central-part-4-troubleshooting/
    title: Agents in Business Central – part 4 – troubleshooting
    date: "2026-02-20"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://www.bertverbeek.nl/blog/2026/02/20/agents-in-business-central-part-4-troubleshooting/
    title: Agents in Business Central – part 4 – troubleshooting
    date: "2026-02-20"
    commit: null
    t: null
    quote: Because no matter how well you design an agent, there will be moments where it doesn't behave as expected.
  - kind: blog
    url: https://www.bertverbeek.nl/blog/2026/02/20/agents-in-business-central-part-4-troubleshooting/
    title: Agents in Business Central – part 4 – troubleshooting
    date: "2026-02-20"
    commit: null
    t: null
    quote: Agent then will try to solve the error. So actionable error messages will be perfect.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "1263"
source_id: bertverbeek-nl
source_name: Discover MS BC - Bert Verbeek
url: https://www.bertverbeek.nl/blog/2026/02/20/agents-in-business-central-part-4-troubleshooting/
published_at: "2026-02-20T09:00:00.000Z"
author: Bert Verbeek
full_text: false
words: 464
quotes:
  - text: Because no matter how well you design an agent, there will be moments where it doesn't behave as expected.
    why_it_matters: Establishes that troubleshooting is an essential skill for agent builders, not an edge case
  - text: Agent then will try to solve the error. So actionable error messages will be perfect.
    why_it_matters: Shows that error messages serve the agent as instructions, not just users, requiring a different design approach
code_objects_mentioned: []
systems:
  - copilot
  - administration
  - development
versions_mentioned: []
preview:
  embeddable: true
  frame_url: https://www.bertverbeek.nl/blog/2026/02/20/agents-in-business-central-part-4-troubleshooting/embed/
  image: https://www.bertverbeek.nl/wp-content/uploads/2026/02/d365businesscentral_512x512.png
  image_alt: null
  image_w: null
  image_h: null
  site_name: Discover Microsoft Business Central - The wonderful world of Business Central
  favicon: https://www.bertverbeek.nl/wp-content/uploads/2026/02/d365businesscentral_256x256.png
  probed_at: "2026-10-07T11:50:35.208Z"
---

# Agents in Business Central – part 4 – troubleshooting

[Read the post](https://www.bertverbeek.nl/blog/2026/02/20/agents-in-business-central-part-4-troubleshooting/) · Discover MS BC - Bert Verbeek (Bert Verbeek) · 2026-02-20 · 464 words · tier community · reviewed (checked by Opus)

> This post explains how to troubleshoot Business Central agents when they don't behave as expected. It covers diagnostic tools like the Agent Consumption page and Agent Task Log, and identifies common pitfalls including unclear error messages, poorly written tooltips, excessive fields, and duplicate captions that confuse agents.

## Key points

- Use the Agent Consumption page to monitor credit usage and communicate costs to users
- Review Agent Task Log details to see what the agent observed, remembered, and accessed
- Write clear, actionable error messages that explain both the problem and how to solve it
- Keep tooltips precise since agents read them to understand fields
- Minimize fields and actions, and avoid duplicate captions that confuse the agent

## Quotes

- "Because no matter how well you design an agent, there will be moments where it doesn't behave as expected." (Establishes that troubleshooting is an essential skill for agent builders, not an edge case)
- "Agent then will try to solve the error. So actionable error messages will be perfect." (Shows that error messages serve the agent as instructions, not just users, requiring a different design approach)

## Context

- Features: Agent Consumption page, Agent Task Log, View details option, What the agent saw section

Source: Discover MS BC - Bert Verbeek, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.