> 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/console/console-operator/console-operator-faqs-and-troubleshooting.md).

# Console Operator: FAQs & Troubleshooting

Answers to common Console Operator questions, and fixes for agents it won't use, missing connections, stalled work, and schedules.

This page answers common questions about the Console Operator, its agents and connections, Schedules, and Gates. Use the troubleshooting entries when the Operator doesn't use an agent or connection, work doesn't finish, or a schedule doesn't run as expected.

## FAQs

### Conversations

<details>

<summary>Does the Console Operator ask before it acts?</summary>

No. It dispatches as soon as you ask; there's no approval step. The Governance Operator in Control Center is the one that stages changes for approval. See [Console Operator](/ai-workbench-qore/console/console-operator.md#at-a-glance).

</details>

<details>

<summary>Can colleagues see my conversations?</summary>

No. Conversations are specific to each user; you see only the ones you started. See [Work in a conversation](/ai-workbench-qore/console/console-operator.md#work-in-a-conversation).

</details>

<details>

<summary>What does the Operator work on?</summary>

The selected project. Everything it creates belongs to that project, and switching projects changes what it can reach. See [What it does](/ai-workbench-qore/console/console-operator.md#what-it-does).

</details>

<details>

<summary>Do the model and effort I choose apply to the agents it hands work to?</summary>

No. They apply to the Operator only, per message. Agents it hands work to, such as the App Builder Agent, run on their own configured model and effort. See [The composer](/ai-workbench-qore/console/console-operator.md#the-composer).

</details>

<details>

<summary>Can the Operator add or remove people or teams?</summary>

No. It can tell you who is in the account and which teams it has, but changes stay in [Users](/ai-workbench-qore/control-center/admin/users.md) and [Teams](/ai-workbench-qore/control-center/admin/teams.md). See [What it does](/ai-workbench-qore/console/console-operator.md#what-it-does).

</details>

<details>

<summary>Does long work stop if I leave the conversation?</summary>

No. Builds such as an app or a knowledge base run as background tasks, and the Operator reports the real outcome when they finish. **Continue in a new conversation** and **Stay here** both leave the work running. See [Long-running work](/ai-workbench-qore/console/console-operator.md#long-running-work).

</details>

### Agents and connections

<details>

<summary>Which agents does the Operator use?</summary>

**System** agents, provided with Qore, start on. Your own project agents start off, so the Operator never hands work to one until you turn it on. The setting applies to you, in this project. See [Agents](/ai-workbench-qore/console/console-operator/agents-and-connections.md#agents).

</details>

<details>

<summary>Can I edit the System agents?</summary>

No. They're preconfigured for the account. You can turn each one on or off for yourself. See [What you control](/ai-workbench-qore/console/console-operator.md#what-you-control-and-what-you-dont).

</details>

<details>

<summary>Does a connection in Integrations Hub let the Operator use it?</summary>

Not on its own. Every connection starts off in the Operator; turn it on under **Connections**. The setting applies to every conversation. Agents the Operator hands work to don't inherit its connections. See [Connections](/ai-workbench-qore/console/console-operator/agents-and-connections.md#connections).

</details>

### Schedules and Gates

<details>

<summary>Which time zone do schedules use?</summary>

UTC. The schedules list then shows the next run in your local time. See [Create a schedule](/ai-workbench-qore/console/console-operator/schedules.md#create-a-schedule).

</details>

<details>

<summary>Can I run a schedule now?</summary>

There's no **Run now**. Ask the Operator in a conversation to run the same instructions straight away. See [Manage schedules](/ai-workbench-qore/console/console-operator/schedules.md#manage-schedules).

</details>

<details>

<summary>Can I see a colleague's schedules or Gates?</summary>

No. Schedules lists only the schedules you created, from every project. Gates lists only conversations you started, and only you can answer them. See [Schedules](/ai-workbench-qore/console/console-operator/schedules.md#manage-schedules) and [Gates](/ai-workbench-qore/console/console-operator/gates.md).

</details>

<details>

<summary>Are Console and Control Center schedules and Gates the same?</summary>

No. Console's run and list Console Operator conversations; Control Center's run and list Governance Operator conversations. See [Gates](/ai-workbench-qore/console/console-operator/gates.md).

</details>

## Troubleshooting

### Conversations

<details>

<summary>I can't see a colleague's conversation</summary>

Conversations are specific to each user. See [Work in a conversation](/ai-workbench-qore/console/console-operator.md#work-in-a-conversation).

</details>

<details>

<summary>Something I started hasn't finished</summary>

Check **Gates** in the top bar: the conversation may be waiting for your answer, and nothing moves until you answer. See [Gates](/ai-workbench-qore/console/console-operator/gates.md).

</details>

<details>

<summary>"This is taking a while" appears above the composer</summary>

The turn is running long. Select **Continue in a new conversation** to carry on with a summary, or **Stay here**. The work keeps running either way. See [Long-running work](/ai-workbench-qore/console/console-operator.md#long-running-work).

</details>

<details>

<summary>The context gauge is nearly full</summary>

Start a new conversation. See [The composer](/ai-workbench-qore/console/console-operator.md#the-composer).

</details>

### Agents and connections

<details>

<summary>The Operator didn't use my agent</summary>

Your own agents start off. Turn it on under **Agents** › **User**. Agents on an older runtime aren't listed until they're moved to the current one. See [Agents](/ai-workbench-qore/console/console-operator/agents-and-connections.md#agents).

</details>

<details>

<summary>I can't turn an agent off</summary>

An agent can't be turned off while it's working on a run. Try again when its run finishes. See [Agents](/ai-workbench-qore/console/console-operator/agents-and-connections.md#agents).

</details>

<details>

<summary>The Operator says it has nothing to hand the work to</summary>

Every agent is turned off. Turn on the agents you need under **Agents**. See [Agents](/ai-workbench-qore/console/console-operator/agents-and-connections.md#agents).

</details>

<details>

<summary>The Operator says it has no connection for a system</summary>

Turn on the connection it names under **Connections**, or connect one from **All integrations**. A new connection appears turned off until you turn it on. See [Connect a new system](/ai-workbench-qore/console/console-operator/agents-and-connections.md#connect-a-new-system).

</details>

<details>

<summary>Connections reads "No connections configured for this project"</summary>

The project has no Integration Hub connections yet. Connect one from **All integrations**. See [Connections](/ai-workbench-qore/console/console-operator/agents-and-connections.md#connections).

</details>

### Schedules

<details>

<summary>A schedule won't save</summary>

**Name** and **Instructions** are required, and a name of only spaces isn't accepted. In **JSON** mode, the instructions must be a non-empty JSON object. See [Create a schedule](/ai-workbench-qore/console/console-operator/schedules.md#create-a-schedule).

</details>

<details>

<summary>A schedule ran at the wrong time</summary>

Schedule times are in UTC. Convert from your local time. See [Create a schedule](/ai-workbench-qore/console/console-operator/schedules.md#create-a-schedule).

</details>

<details>

<summary>A schedule didn't run</summary>

Check that it's **Active**, not **Paused**. If the Operator a schedule runs isn't active, the run is skipped. See [Notes and limitations](/ai-workbench-qore/console/console-operator/schedules.md#notes-and-limitations).

</details>

<details>

<summary>A scheduled run didn't do what I expected</summary>

Nobody is present to answer its questions. Put everything the run needs in the instructions, and check which agents **Agents this run may use** allows. See [Notes and limitations](/ai-workbench-qore/console/console-operator/schedules.md#notes-and-limitations).

</details>

<details>

<summary>A schedule action is unavailable</summary>

Creating and changing schedules needs a role that allows it; hover over the action for the reason. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

### Related

* [Console Operator](/ai-workbench-qore/console/console-operator.md), [Agents & connections](/ai-workbench-qore/console/console-operator/agents-and-connections.md), [Schedules](/ai-workbench-qore/console/console-operator/schedules.md), and [Gates](/ai-workbench-qore/console/console-operator/gates.md)
* [Use the Console Operator](/ai-workbench-qore/task-guides/use-the-console-operator.md): every Console Operator task
* [Governance Operator FAQs](/ai-workbench-qore/control-center/governance-operator.md#faqs)

***

{% 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/console/console-operator/console-operator-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.