Troubleshooting
Find the right recovery steps from the message or behavior you see in Titan.
Start with the message on the affected page. Check whether the information is current or marked stale before changing your setup.
| Problem | Start here |
|---|---|
| Cannot register, sign in, or obtain access | Your Titan account |
| PC Agent offline, pairing stalled, or phone missing | Connection problems |
| Computer dependency needs attention | Host Deps |
| Phone visible but not ready | Device readiness |
| Supervision or trust repair did not finish | Device supervision |
| Queue waiting, run failed, or result uncertain | Automation problems |
| AI provider disconnected or test failed | AI adapters |
| Resource missing or wrong version selected | Resources |
| Assistant cannot connect or an MCP tool is forbidden | MCP connection |
| Need help from the Titan team | Contact support |
Refresh reads before repeating changes
Retry on a failed list usually reloads information. Repeating a create, start, erase, or delete action can have a different effect. If the result of a change is unconfirmed, read the current state before deciding whether to repeat it.
Check the connection path
Work through these checks in order:
- Can you sign in and load current data from Titan?
- Is the PC Agent connected?
- Are its Host Deps checks current and healthy?
- Is the intended phone connected, trusted, and ready?
- Are the selected adapter and resources available for the intended work?
This helps distinguish a browser connection issue from a host, phone, or workflow issue.
Preserve useful evidence
Keep the exact message, affected record IDs, and approximate time. Where Titan shows a support reference, include it. Use the support checklist to send useful details without exposing credentials.