On this page
Troubleshooting
Recover from project context problems, interrupted work, unavailable connections, failed checks, and plan issues.
When a task does not behave as expected, start with the visible project and task context. The right recovery depends on whether the issue is scope, processing, an external connection, a project check, or your account plan.
Confirm the visible context
Check the open folder or repository, selected files, attachments, project, and settings against the request.
Read the visible state
Identify whether work is loading, processing, stopped, failed, or waiting for a connection or decision.
Choose the smallest recovery
Correct the scope, retry the relevant action, continue without an optional connection, or start a new focused task.
| Problem | First check | Next step |
|---|---|---|
| Incomplete context | Folder, roots, files, and attachments | Add only the missing focused context. |
| Interrupted work | Visible activity and existing changes | Clarify, retry, or begin a new task. |
| Unavailable connection | Selected MCP server and task need | Reconnect or continue from project context. |
| Missing or failed check | Project tooling and failure detail | Review files and correct configuration or scope. |
The project context is wrong or incomplete
Confirm that the relevant folder or repository is open and that the task names the files or area that matter. If the change crosses folders, review Files and workspaces. Add focused files or images through Context and attachments rather than attaching unrelated material.
Work was interrupted or stopped
Read the visible task activity and inspect any resulting changes before trying again. Clarify the request, send a focused follow-up, or start a new task when the goal has changed. Conversations and tasks explains queued follow-ups and stop behavior.
An external connection is unavailable
Check that the intended optional connection is selected and that the task actually needs it. Retry when appropriate, or continue from project context if the external tool is not required. Review MCP Servers for task-scoped connection guidance.
A check is missing or failed
Check whether the project provides the relevant command and whether the failure points to the change, project configuration, or an unavailable tool. Review changed files even when a check passes; see Changes and verification.
What if a plan or artifact is unexpected?
A plan is not required for every task, and larger work can expose different artifacts depending on what needs alignment. Re-read the request and visible scope, then correct the direction before continuing.
For billing or plan issues, review Billing and usage. If visible details do not explain what happened, use the support actions below and include only the information needed to reproduce the issue.
Report a documentation problem or contact the RevampKey team.