AgentQ Troubleshooting

This page documents the known problems with AgentQ and the steps to resolve them. Each section describes a symptom, its cause, and the resolution.

Setting It Up

The AgentQ Page Shows a Preview Instead of a Chat

The page opens on a board headed Ask about your data. Act on the answer. and there is nowhere to type.

Cause: No AI provider is connected yet. The preview is what the page shows until one is.

Resolution: A Manager or Admin connects a provider from that same page. See Add Integration. Everyone else sees a note saying an administrator connects a provider once and it turns on for all, so there is nothing to do but ask for it.

The Manage group at the bottom of the sidebar shows the provider status but no Settings entry.

Cause: Opening the settings needs the Manager or Admin role. The entry is hidden for everyone else rather than shown and refused.

Resolution: Ask a Manager or an Admin to make the change. The Audit entry beside it is stricter still, needing the Admin role and a connected provider.

The Connection Is Refused When Saving

Connect AgentQ or Save changes does not complete, and the page shows an error.

Cause: The credentials are tested against the provider before anything is stored, so the provider's own refusal is what you are reading, most often an invalid or revoked key, an exhausted quota, or a model name the account cannot reach.

Resolution: The message comes from the provider verbatim, so act on what it says. Check the key, the account's credits, and that the model is available to it. Easy setup avoids all three, since it runs on Qualytics AI with no key of your own.

Continue Is Disabled on the Connection Tab

The action bar reads Finish the Connection tab to continue.

Cause: A required field is still empty. Business Context is required on both setup paths, and the field shows Business Context is required when it is left blank.

Resolution: Fill in the remaining fields. Business Context takes up to 2,000 characters and describes your organization's data quality focus, which AgentQ uses to make answers relevant.

Using AgentQ

AgentQ Is Not Responding

A message is sent and nothing comes back.

Cause: Either no provider is connected, the provider is rejecting the request, or a limit was reached.

Resolution: Open AgentQ and read the Manage group at the bottom of its sidebar, where the status dot and the provider name, or Not connected, say whether a provider is connected. For an external provider, check that the key is valid and the account has credits. Rate limits and token limits are listed on AgentQ Limits, and a request that hit one succeeds after a short wait or when broken into smaller steps.

The Response Was Cut Off Mid-Way

The answer stops in the middle of a sentence or a list.

Cause: The request reached a token limit, or the stream stalled long enough for the inactivity watchdog to end it.

Resolution: Break the request into smaller, more focused prompts, start a fresh conversation with more specific context, or configure a more capable model under Custom setup.

A Request Was Declined as Off-Topic

AgentQ answers that the request is outside what it covers.

Cause: The topic guardrail, which keeps AgentQ to data quality, governance, and the platform itself. It occasionally misreads an edge case.

Resolution: Rephrase with explicit context, naming a datastore, container, or quality check. The guardrail is not configurable, because turning it off would weaken the deployment rather than restrict it.

The Answers Are Not About the Right Asset

AgentQ answers about something other than what you meant.

Cause: Without an asset in context, the request is read on its own words.

Resolution: Open AgentQ from the page of the asset you mean, so its context is injected automatically, and name the datastore and table in the request. For a multi-step task, ask for one step at a time and check the result before the next.

A Tool Call Failed

The response shows a step that did not complete.

Cause: Usually permissions. Every tool runs as you, so a datastore you cannot reach is a datastore AgentQ cannot reach on your behalf.

Resolution: Click the step in the response to expand it and read the error under Output. Check your role and your team permissions on the datastore involved. See Permissions.

Capabilities That Are Switched Off

A Capability Says It Needs a Level

AgentQ answers with something like Golden-record recommendations needs Source Data Shared, and your Qualytics Administrator has not enabled it.

Cause: This is not an error and not about your own access. The deployment's data sharing level does not cover that capability, and AgentQ says so rather than quietly returning a weaker answer.

Resolution: Ask an administrator to raise the level on the Access Control tab. The message names the level that would restore the capability. See Configure Access Controls and Access Controls.

The Sparkle Is Missing From a Description Field

The control that suggests a description does not appear.

Cause: Either no AI provider is configured, in which case the sparkle is hidden everywhere, or the level is below Metadata shared, which is what description suggestions need.

Resolution: Connect a provider, or raise the level. On most surfaces the sparkle also follows the permission to edit that description, so a field you cannot edit shows no sparkle either.

The Attach Button Is Missing

There is no way to attach a file to a message.

Cause: The active AI provider does not support file uploads. The button is only shown for the providers that do.

Resolution: Paste the content as text instead, which AgentQ captures as an attachment past 1,000 characters. The providers that accept files are listed on Chat Interface Tips.

Prompt Suggestions Are Generic or Absent

A new conversation opens without the usual suggestions.

Cause: Suggestions are built from the containers with the most active anomalies, so a workspace without anomalies has little to build from. They are also hidden when the chat is opened with an asset already in context, so the scoped question is not competing with them.

Resolution: Run a scan to generate anomalies, or type the request directly. Neither case blocks anything.

Limitations

Limitation	Detail
One provider for the whole deployment	The configuration is deployment-wide, not per user, and only one provider is active at a time.
Quality checks on a new computed asset wait for a profile	A computed table, file, or join has to finish profiling before checks can be created on it. AgentQ can run the profile and wait as part of the request.
The topic guardrail and context compression cannot be turned off	Both are part of how a turn works. Disabling them would weaken the deployment rather than restrict it.
Access levels do not apply to external AI clients	A client you connect over MCP brings its own model, so the deployment's sharing level does not govern the existing tools on that path. Access there follows your own role and team permissions.