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

Does the Console Operator ask before it acts?

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.

Can colleagues see my conversations?

No. Conversations are specific to each user; you see only the ones you started. See Work in a conversation.

What does the Operator work on?

The selected project. Everything it creates belongs to that project, and switching projects changes what it can reach. See What it does.

Do the model and effort I choose apply to the agents it hands work to?

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.

Can the Operator add or remove people or teams?

No. It can tell you who is in the account and which teams it has, but changes stay in Users and Teams. See What it does.

Does long work stop if I leave the conversation?

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.

Agents and connections

Which agents does the Operator use?

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.

Can I edit the System agents?

No. They're preconfigured for the account. You can turn each one on or off for yourself. See What you control.

Does a connection in Integrations Hub let the Operator use it?

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.

Schedules and Gates

Which time zone do schedules use?

UTC. The schedules list then shows the next run in your local time. See Create a schedule.

Can I run a schedule now?

There's no Run now. Ask the Operator in a conversation to run the same instructions straight away. See Manage schedules.

Can I see a colleague's schedules or Gates?

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 and Gates.

Are Console and Control Center schedules and Gates the same?

No. Console's run and list Console Operator conversations; Control Center's run and list Governance Operator conversations. See Gates.

Troubleshooting

Conversations

I can't see a colleague's conversation

Conversations are specific to each user. See Work in a conversation.

Something I started hasn't finished

Check Gates in the top bar: the conversation may be waiting for your answer, and nothing moves until you answer. See Gates.

"This is taking a while" appears above the composer

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.

The context gauge is nearly full

Start a new conversation. See The composer.

Agents and connections

The Operator didn't use my agent

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.

I can't turn an agent off

An agent can't be turned off while it's working on a run. Try again when its run finishes. See Agents.

The Operator says it has nothing to hand the work to

Every agent is turned off. Turn on the agents you need under Agents. See Agents.

The Operator says it has no connection for a system

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.

Connections reads "No connections configured for this project"

The project has no Integration Hub connections yet. Connect one from All integrations. See Connections.

Schedules

A schedule won't save

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.

A schedule ran at the wrong time

Schedule times are in UTC. Convert from your local time. See Create a schedule.

A schedule didn't run

Check that it's Active, not Paused. If the Operator a schedule runs isn't active, the run is skipped. See Notes and limitations.

A scheduled run didn't do what I expected

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.

A schedule action is unavailable

Creating and changing schedules needs a role that allows it; hover over the action for the reason. See Roles.

Related

• Console Operator, Agents & connections, Schedules, and Gates
• Use the Console Operator: every Console Operator task
• Governance Operator FAQs

---

Maintained by Abhishek Paul AI-assisted, human-approved