> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/control-center/govern/govern-faqs-and-troubleshooting.md).

# Govern: FAQs & Troubleshooting

Answers to common Govern questions, and fixes for stopping agents, connector access, and governed graph uploads.

This page answers common questions about Agent Controls, Connectors, Governed Graph, and Publish Review. Use the troubleshooting entries when you can't stop an agent, a connector isn't available, or a graph upload fails.

## FAQs

### Agent Controls

<details>

<summary>Who can stop agents?</summary>

**Stop agents** and **Resume agents**: Account Admin and Organisation Admin. Governance Manager and Auditor can view Agent Controls but can't stop or resume agents. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

<details>

<summary>Does stopping an agent disable it?</summary>

No. **Stop** aborts the agent's in-flight runs, and work in progress is lost. New runs can start again at any time, and the agent runs again after its next trigger. Agent Controls doesn't edit, disable, delete, or deactivate agents. See [Agent Controls](/ai-workbench-qore/control-center/govern/agent-controls.md#read-the-list).

</details>

<details>

<summary>Can I stop a selected group of agents?</summary>

No. Stop agents one at a time, or select **Stop all agents** to interrupt every agent's active runs. **Stop all agents** asks you to confirm and can't be undone. See [Stop every agent](/ai-workbench-qore/control-center/govern/agent-controls.md#stop-every-agent).

</details>

<details>

<summary>What happens when I stop a system agent?</summary>

System agents, such as the Operator and the builder agents, are listed alongside your own. Stopping one also stops every run and helper agent it started. **Stop** is their only action. See [Stop a system agent](/ai-workbench-qore/control-center/govern/agent-controls.md#stop-a-system-agent).

</details>

### Connectors

<details>

<summary>What does Connectors control?</summary>

It's the account-wide register of what an agent may reach outside itself: integrations, MCP servers, and platform skills. Every agent inherits it as its outer limit: an agent can't use a connector the account hasn't made available. See [Connectors](/ai-workbench-qore/control-center/govern/connectors.md).

</details>

<details>

<summary>Why does the same MCP server appear several times?</summary>

There's one row for each connection an agent has made, so a server appears once for each agent that connects to it, with that agent's project. See [MCP servers](/ai-workbench-qore/control-center/govern/connectors.md#mcp-servers).

</details>

### Governed Graph

<details>

<summary>Who can upload a governed graph?</summary>

**Manage govern graphs**: Governance Manager, Account Admin, and Organisation Admin. Approver and Auditor can view graphs only. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

<details>

<summary>How do I update or delete a graph?</summary>

Upload the revised package as a new graph; **Edit** changes only the name. A graph can't be deleted from the page: the row menu has View, Download, and Edit only. See [Governed Graph FAQ](/ai-workbench-qore/control-center/govern/governed-graph.md#faq).

</details>

<details>

<summary>How does an agent use a governed graph?</summary>

A completed graph becomes knowledge in the account. Attach that knowledge to the agent. Attaching the package JSON in the Agent Builder chat doesn't create or attach a graph. See [Governed Graph FAQ](/ai-workbench-qore/control-center/govern/governed-graph.md#faq).

</details>

<details>

<summary>More Governed Graph questions</summary>

Relationship counts, obligation links, sign-off, customer data, and visibility are answered in the [Governed Graph FAQ](/ai-workbench-qore/control-center/govern/governed-graph.md#faq).

</details>

### Publish Review

<details>

<summary>Can I approve publish requests in Publish Review?</summary>

Not yet. Publish Review is coming soon. Apps use the in-product publishing flow. See [Publish Review](/ai-workbench-qore/control-center/govern/publish-review.md).

</details>

## Troubleshooting

### Agent Controls

<details>

<summary>Stop and Stop all agents are disabled</summary>

Hovering shows *You don't have access to stop agents*. Stopping agents needs the **Stop agents** capability: Account Admin or Organisation Admin. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

<details>

<summary>"Stopping the agent's executions" stays on screen, or appears twice</summary>

It doesn't mean work is still going on. The request runs once, even when the agent had no active runs. See [Stop a running agent](/ai-workbench-qore/control-center/govern/agent-controls.md#stop-a-running-agent).

</details>

<details>

<summary>View Agent is missing for an agent</summary>

**View Agent** isn't offered for system agents, which show `—` in **Project**. See [Stop a system agent](/ai-workbench-qore/control-center/govern/agent-controls.md#stop-a-system-agent).

</details>

<details>

<summary>I can't bookmark a page of the agent list</summary>

The page number isn't saved in the URL. Search is: it's saved as `?search=<term>`, so search for the agents and share that view. See [Find agents](/ai-workbench-qore/control-center/govern/agent-controls.md#find-agents).

</details>

### Connectors

<details>

<summary>An agent can't use an integration or MCP server</summary>

The account sets the outer limit. An agent can't use a connector the account hasn't made available, whatever its own configuration requests. Check the connector's **Standing** in Connectors. See [Connectors](/ai-workbench-qore/control-center/govern/connectors.md).

</details>

<details>

<summary>A key is visible in an MCP server's URL</summary>

Connectors shows each URL in full. Edit the connection in the agent and enter a `$secret.` reference instead of the key. See [How catalog fields are used](/ai-workbench-qore/console/agent-builder/build/mcp-tools.md#how-catalog-fields-are-used).

</details>

### Governed Graph

<details>

<summary>Upload Govern Graph isn't available, or the upload is refused</summary>

Uploading needs the **Manage govern graphs** capability: Governance Manager, Account Admin, or Organisation Admin. Without it, the tooltip reads *You don't have access to upload govern graphs*. See [Governed Graph troubleshooting](/ai-workbench-qore/control-center/govern/governed-graph.md#troubleshooting).

</details>

<details>

<summary>The upload failed</summary>

Hover over the **Failed** badge for the reason, fix the package, and upload it again. Only `.json` files up to 80 MB can be selected. Each reason and its fix is listed in [The upload failed](/ai-workbench-qore/control-center/govern/governed-graph.md#the-upload-failed).

</details>

<details>

<summary>The agent says it has no governance graph to query</summary>

No governed graph is attached to the agent. Attach it as knowledge. See [Attaching a governed graph](/ai-workbench-qore/console/agent-builder/build/attaching-knowledge-to-an-agent.md#attaching-a-governed-graph).

</details>

<details>

<summary>An agent's answer from the graph looks incomplete</summary>

Knowledge Graph Search returns at most 25 rows per query, and tells the agent when more matches exist. Ask a narrower question. See [Common questions](/ai-workbench-qore/control-center/govern/governed-graph.md#common-questions).

</details>

### Related

* [Agent Controls](/ai-workbench-qore/control-center/govern/agent-controls.md), [Connectors](/ai-workbench-qore/control-center/govern/connectors.md), [Governed Graph](/ai-workbench-qore/control-center/govern/governed-graph.md), and [Publish Review](/ai-workbench-qore/control-center/govern/publish-review.md)
* [Govern agents and models](/ai-workbench-qore/task-guides/govern-agents-and-models.md): every Govern task
* [Audit Trails](/ai-workbench-qore/control-center/observe/audit-trails.md): who changed what

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/ai-workbench-qore/control-center/govern/govern-faqs-and-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
