FAQ and Support
About 2 min
FAQ and Support
For installation, startup, or Context configuration issues, see Troubleshooting.
1. Common Messages
| Message | Action |
|---|---|
| Account locked | Wait for the lock to expire or ask an administrator to unlock it |
| Change your password first | Follow the prompt before continuing |
| Account has no database Context | Ask a platform administrator to configure data access |
| Conversation is generating a response | Wait or click Stop Generating; check whether you sent a message in another tab |
| Approval expired or timed out | Confirm the original operation did not execute, then request it again for a new review |
| Statement rejected | Contact the approver; do not simply resubmit |
| Daily budget exhausted | Contact an administrator or wait until the next day |
| Context too long | Generate a summary or create another conversation |
| Upload failed or file too large | Compress or split materials, or ask an administrator to inspect limits |
| Internal service error with an ID | Record the ID, time, conversation title, and steps for your administrator |
| No permission to use an agent or knowledge base | Ask an administrator to inspect user groups and access scopes |
| Tool not enabled for this agent | Ask an administrator to enable it in agent settings or use another agent |
| Older conversation automatically summarized | The system created a summary; recent conversation content remains usable |
| Timecho AI key not configured | Forecasting is unavailable; contact the platform administrator |
| Connection target does not match the managed password | Ask an administrator to check the connection and set the password again in Execution Channels |
| Scan recognition failed or read only some pages | Verify image understanding support, split documents exceeding the page limit, and inspect unread pages |
| External tool list empty or invocation failed | Ask an administrator to check the URL, authorization, network, and whether the agent has enabled the service |
| Request lacks a valid anti-CSRF token | Refresh and retry; use API tokens for scripts |
| Sign-in or password changes are too frequent | Wait and retry. If many users are affected, ask operations staff to check the proxy's real-IP configuration |
Follow the guidance for failed queries. For failed writes or deletes, inspect approval and actual data state before retrying to avoid duplicate execution.
2. Get Support
| Situation | Contact |
|---|---|
| Forgotten password, locked account, unconfigured data access, or insufficient budget | Your organization's platform administrator |
| Approvals, database permissions, or verification of operation results | Your organization's database administrator |
| Installation packages, compatibility, deployment approaches, unresolved issues, or failed recovery/upgrades | Timecho team |
For additional API integration, data import, forecasting, or deployment options, contact the Timecho team to confirm supported versions and scope.
Use your project contact or established service channel. Provide:
- Version information from About and the deployment method.
- Time of occurrence, reproduction steps, and expected result.
- Error text and IDs, with necessary logs or screenshots.
- Production impact, whether writes have occurred, and actions already taken.
Sanitize screenshots and logs first. Do not send passwords, API keys, sign-in tokens, complete .env files, or unnecessary business details. Preserve evidence for urgent issues; do not repeatedly execute writes or remove volumes without verification.