ONCUE / GUIDE
Troubleshooting
First identify whether the issue is access, sandbox startup, agent execution, or review evidence. The next useful step depends on that distinction.
A repository is missing
Confirm the connected GitHub account and installation. Check that the installation grants access to the repository you expect. Refresh the repository list after correcting access.
If the source link from this website returns a 404, the repository may simply be private to your account.
The remote workspace will not start
Check the Modal connection and the session’s startup error. Confirm compute configuration and provider availability. A workspace startup failure is different from the model rejecting a request.
Avoid repeated retries without reading the error; they may repeat the same failing setup.
The model request fails
Check the selected model, credential type, provider quota, and the integrations enabled for that deployment. A model visible in one harness is not automatically usable in every harness.
Reconnect credentials through the intended connection flow rather than pasting a replacement into the session.
Checks fail or do not run
Read the command and its output. Verify that the repository’s install and check scripts are valid in the remote environment, and that required development secrets are configured.
Missing check evidence is not a passing result. Fix configuration or the underlying change and review fresh evidence for the new revision.
The interface differs from a demo
OnCue is evolving, and recordings can show an older revision. The source records distinguish built features from planned work. Live previews, shared workspaces, built-in subscriptions, and other roadmap items should not be assumed available.
When reporting an issue, include the revision, session state, relevant error, and reproduction steps. Remove credentials and private content first.