Troubleshooting AI agents

 

 

Who can use this feature
gray-cloud.svgAvailable on monday AI platform, availability on all products coming soon

This article covers how to investigate and resolve issues with your AI agent. Agents run continuously based on your defined instructions, permissions, and triggers, and act on your boards and connected tools. If your agent behaves unexpectedly, does not run when you expect it to, or produces results that need refining, use the guidance below to identify the cause and take action.

For a full overview of AI agents, see the AI Agents on monday.com article.

 

How to troubleshoot your agent

Agents continuously evaluate and act based on the provided instructions, meaning that they run in a continuous loop.

If the agent performs unexpected actions outside of your definition scope or appears to be stuck in a loop:

  • Use the abort / stop button to stop the run
  • Revisit and refine instructions in the Brain tab to ensure they detail exactly what you want your agent to accomplish
  • If everything is defined correctly but the behavior persists, reach out to support for help

Note that any changes or updates made while an agent is running will not affect the current run and will only apply to subsequent runs.

Before escalating an issue, you can usually investigate agent behavior directly in the product. The agent setup is shown in a readable format, so you can review its instructions, permissions, tools, and connected resources without needing technical expertise.

You can also open the Activity tab to review each run, including what the agent did, when it ran, and why it took a particular action.

 

How can you troubleshoot an AI agent?
  • Review the agent's configuration in the UI to understand its permissions, tools, and prompts
  • Go to the Activity tab and open the run log
  • Review the agent's thought process, plan, and actions
  • Confirm triggers, conditions, and inputs are correctly defined
  • Ensure relevant boards, docs, and integrations are connected and accessible
Why can't the agent access a board or data?
  • Confirm the agent has been granted access to the relevant boards or docs
  • Verify the creator of the agent has access to those resources
  • Check if any recent permission changes were made
  • Reconnect or reconfigure the resource in the agent setup if needed
Why did the agent perform an action it shouldn't?
  • Review the agent's configured actions and logic
  • Check if permissions allow broader actions than intended
  • Validate triggers and conditions that led to the action
  • Adjust configuration to restrict unwanted behavior
  • Run the agent in Preview Mode to validate behavior (will be relevant when preview tab is restored)
Why didn't the agent perform an action it should?
  • Review triggers and ensure conditions are correctly defined
  • Confirm the triggering event actually occurred
  • Check for missing inputs or required fields
  • Validate setup
Why are the agent's results incomplete or incorrect?
  • Review the instructions or prompt given to the agent
  • Ensure relevant data sources are connected
  • Check for ambiguous or conflicting instructions
  • Test with a simplified input to isolate the issue
Why is the agent not triggering?
  • Confirm trigger conditions are correctly defined
  • Check that the triggering event actually occurred
  • Verify the agent is not paused
  • Review the Activity tab for attempted runs
Why can't you access or run the agent?
  • Verify you have permission to access the agent (viewer or editor)
  • Confirm the agent has been shared with you
  • Check workspace or account-level restrictions
  • Re-share the agent if needed
Why are the agent's actions unclear or unexpected?
  • Go to the Activity tab
  • Review what the agent did, when, and why
  • Cross-check with the configured logic
  • Adjust configuration if behavior is not aligned
What should you do if you have concerns about data security or access?
  • Ask clarifying questions to understand the concern (such as data exposure, permissions, or integrations)
  • Review which boards, docs, and integrations are connected
  • Confirm the agent operates within existing and defined permissions
  • Restrict access to sensitive resources if needed
Why does the agent work in preview but fail live?
  • Compare Preview Mode versus live conditions (data and triggers)
  • Check if live data meets trigger conditions
  • Verify permissions in the live environment
  • Re-run tests with real scenario inputs
Why were credits charged for an agent run?
  • Review what actions the agent performed during the run
  • Check which features or tools were used
  • Correlate usage with credit consumption logic
  • Set expectations for how similar runs may be charged going forward
Why can't the agent be edited or managed?
  • Confirm you have editor permissions
  • Identify the current owner of the agent
  • Note that ownership cannot be transferred
Why is the agent triggering itself in a loop?

Agents are blocked from triggering themselves to prevent unintentional credit consumption. For example, a rule like "every time an item is created, create an item." When a self-trigger is blocked, an explanation appears in the Activity tab along with a notification containing fix instructions. Review and update your trigger configuration to resolve the loop.

 

Tip: In many cases, the fastest way to troubleshoot an AI agent is to compare the configured instructions and permissions in the Brain tab with the run details in the Activity tab.

If you have any questions, please reach out to our team right here. We’re available 24/7 and happy to help.

Last modified on

Still have questions?
We can help.

Chat support

Get in touch with our support team through our chat for any questions, concerns, or inquiries.

Community forum

Learn, share ideas and connect with other monday.com customers.

Expert help

Hire a monday.com expert to optimize your workflows.

Is this article helpful?
Help us improve our articles.