Bot troubleshooting - Cortex Docs

Bot names its states plainly. This page maps them to causes and fixes. For the rest of the app see Troubleshooting.

Access

What you see	Cause	Fix
This space is reserved	You are not signed in	Sign in, or Continue in Chat
The public product page at `/bot`	Guests see the product page	Sign in, then choose Bot
The setup form instead of a bot list	The account has no bots yet — a setup, not an empty list	Create a bot

The computer

What you see	Cause	Fix
Connecting on the rail	The Cloud guest is starting	Wait — this state exists only while the guest starts
Stream Unavailable	The guest is running but its live screen is not reachable right now	Choose Open desktop again, or Sleep and wake it with a turn
The first message of a turn takes a moment	The guest hibernated while idle and is being resumed before the model runs	Expected
No This PC option	You are in the browser	Use the Bot desktop app

Tools and approvals

What you see	Cause	Fix
An Allow / Deny / Always widget that does not go away	A consequential step is parked. Nothing runs until you choose.	Read it, then choose
The bot cannot use an app you connected	The connection is enabled for Chat only	Customize → Connectors → enable it for Cortex Bot
A step you allowed once parks again	Allow is for this once; Always remembers that kind of step	Choose Always if you want it remembered
The bot asks you for a credential	`secret_request` — it needs a secret it should never see typed in the transcript	Enter it in the widget

Turns

What you see	Cause	Fix
A long job stops after about 15 minutes	The turn deadline	Split the job, or run it as a routine or background task
A turn stops after repeating the same action	Six consecutive identical tool calls trip the loop guard	Rephrase the task or give the bot the missing information
The bot says nothing after working	It had nothing to send. Plain text outside the user-visible tools is dropped.	Ask it to report — tell me what you found

Routines

What you see	Cause	Fix
A routine fired at an unexpected hour	Routines use your local weekday clock	Check your device’s time zone
A routine did nothing on Saturday	Weekdays only	Expected

Errors

Bot uses the same problem documents as the rest of Cortex. Common ones:

Code	Meaning
`no_capacity`	No guest could be started right now; try again shortly
`concurrency_limit_reached`	Too many bots or turns active at once
`invalid_state`	The bot or its computer is not in a state that allows the action

Full list: Problem catalog.

Computer — the guest states behind Connecting and Stream Unavailable.
Approvals — why a parked step waits.
Routines — local weekday timing.
Troubleshooting — the same guidance across all products.

⌘I