Contact support
Prepare a useful support report with the right IDs, messages, and observations.
Contact Titan support on Telegram, or the administrator who invited you.
Include the relevant details
- What you were trying to do and the result you expected.
- The exact visible message and the approximate time, including your time zone.
- Your user ID, when the issue concerns account access.
- The affected agent, device UDID, strategy, queue, run, or resource ID.
- Whether the displayed information was current, reconnecting, or marked stale.
- The last action you took and whether its result was confirmed.
- Your host OS, agent version, and the App/Service versions from Settings > System, where available.
If Titan displays a Support reference, include it. A screenshot of the affected status or error can help when it does not reveal private data.
For an automation failure
Open My Runs, select the affected attempt, and note the overall outcome and first useful error. Explain whether the phone already completed any part of the task and whether you attempted a retry.
For queue problems, include the queue status, waiting reason, and affected worker or item.
Keep credentials private
Do not send passwords, API key secrets, PC Agent setup codes, provider authorization codes, mailbox tokens, or WiFi passwords in a support report. Remove sensitive material from screenshots and any logs requested by support.
If support needs logs, follow the collection instructions they provide for your host and agent version. Avoid sending an entire application-data folder or a database export.
Example report
Task: Start one item in my prepared queue.
Expected: The selected phone starts the workflow.
Observed: The queue remains waiting for a ready device.
When: Date, time, and time zone.
Queue/run/device: The relevant IDs.
PC Agent: Connected; Host Deps shows one check needing attention.
Message: The exact text of that check.
Last action: Re-check requested; the same result returned.
Versions: App, Service, and agent versions if available.