Common issues and how to resolve them

Quick fixes for the most common questions in Odeus: missing models, Knowledge Hub searches with no results, Drive sync versus connectors, and paused human-in-the-loop runs.

This page covers the issues users hit most often. For file-specific questions, see the FAQ.

A model is missing or greyed out

Odeus runs on a governed model catalog that workspace administrators control. A model may be unavailable because it has not been enabled for your workspace, because a token spend-limit has been reached, or because the provider is still marked coming soon. See model availability for details, and ask a workspace admin to review the catalog if you expect a model to be there.

Knowledge Hub search returns no results

When the assistant cannot find anything for a Knowledge Hub @-reference:

• Confirm the documents finished processing. After upload, files are parsed, chunked, and indexed. Large PDFs take longer; wait until processing completes before searching.
• Check you referenced the right folder. Retrieval only searches the folder(s) you @-mention in the message.
• Make the query more specific. Retrieval is semantic — phrasing the question with the same terms or concepts used in the documents improves the matches.
• Verify the file type. Only supported file types are indexed, and each file must be under the 50 MB limit.

Google Drive sync versus connectors

These are two different things and are a common source of confusion:

• Google Drive sync mirrors a Drive folder into the Knowledge Hub so its contents are indexed for retrieval (refreshed on a schedule). This is the only source that syncs into the Knowledge Hub.
• Connectors (MCP) — Microsoft 365, SharePoint, Slack, Notion, and others — are live tools the assistant calls during a conversation. They are browsed in real time and are not synced or indexed into the Knowledge Hub. OneDrive and Dropbox are not currently synced.

If you expected SharePoint or OneDrive content to be searchable in the Knowledge Hub, use the connector to browse it live instead, or add the files to a Knowledge Hub folder via Google Drive sync or direct upload.

A run is paused or awaiting approval

Odeus supports human-in-the-loop (HITL): an agent or workflow can pause to ask you a clarifying question or to request approval before continuing. A paused run is waiting on you, not stuck.

• Look for the prompt or approval card in the conversation and respond to it. The run resumes from where it paused.
• Pauses are durable — a run can wait indefinitely, so you can come back to it later and still answer.
• For workflows, an approval node holds the run until the request is approved or rejected.

If a run still appears stuck after you respond, reopen the conversation to refresh the live trace.