Troubleshoot agents
Diagnose missing access, weak answers, stale knowledge, Slack silence, and configuration or lifecycle problems.
Start with the surface where the failure is visible, then work inward: access, enabled state, evidence, channel binding, and finally the surrounding Automation.
The Agents page is missing
Symptoms: agents.infra.one redirects unexpectedly or the organization path returns not found.
Check:
- You are signed in to the intended Infra One account.
- The URL contains the correct organization slug.
- The Agents service is enabled for the organization.
- Your user has organization-admin access with permission to manage agents.
A not-found response can be the intentional result of a disabled feature or missing capability.
The agent gives an unsupported or stale answer
- Read the System prompt and confirm it defines uncertainty behavior.
- Find the relevant Knowledge source.
- If it says Never fetched, use Fetch now.
- If it says Error, open the URL outside Infra One and check availability, authentication, redirects, and text content.
- If it says OK, compare the last fetch time with the source edit.
- Ask a question whose answer exists verbatim in the source.
If that direct test passes but the original question fails, narrow the prompt or split a broad source into focused pages.
The agent is silent in Slack
Check in this order:
- The agent card shows Enabled.
- Slack shows Connected to the expected workspace.
- The channel is present on the Slack card.
- The channel is paired with this agent.
- Its mode is Mentions, not Off.
- The bot is a member of the channel.
- Your test actually mentions the bot.
For direct messages, confirm Direct messages selects an agent rather than No DM agent….
An Automation cannot select the agent or channel
The Agent message action shows only enabled agents. After selecting one, Slack channel shows only enabled channels bound to that agent. Fix those states on the Agents service, then reload the Automation form.
A recent change had no effect
- Prompt and settings changes require Save.
- Knowledge edits require a subsequent successful fetch.
- Slack changes must affect the exact workspace and channel used by the interaction.
- An Automation may still be disabled even when its agent is enabled.
When to escalate
Capture the organization slug, agent name, surface, approximate time, expected behavior, actual behavior, knowledge-source state, and—when an Automation is involved—the relevant run status and error category. Never include a signing secret, OAuth token, or confidential conversation body in an ordinary support message.