Troubleshooting
Solutions for common issues with your AI assistant.
Running into problems with your assistant? Here are the most common issues and how to fix them.
"My assistant doesn't remember our conversation"
If the assistant seems to have forgotten context from a previous chat, here's what to check:
- Are you in the same conversation thread? Session memory only works within a single conversation. If you started a new chat, the assistant relies on long-term memory instead.
- Is long-term memory enabled? Go to Assistant > Settings and make sure memory is turned on. If it was recently disabled, the assistant won't have stored context from recent conversations.
- Was the information significant enough? The assistant prioritizes storing preferences, decisions, and recurring context. Casual one-off exchanges may not be retained in long-term memory.
If you want the assistant to remember something specific, try telling it directly: "Remember that I prefer weekly summaries in bullet point format."
"Responses are too generic"
When the assistant's answers feel vague or unhelpful, the issue is usually a lack of context. Try these fixes:
- Be more specific in your requests. Instead of "Help me with marketing," try "Write 3 subject line options for our product launch email targeting enterprise customers."
- Connect your knowledge base. Generic responses often mean the assistant doesn't have your documents to draw from. Check that relevant knowledge sources are connected.
- Add custom instructions. In Settings, add instructions about your role, industry, or preferences. This gives the assistant a baseline context for every conversation.
"The assistant can't access my documents"
If you're asking questions about your documents and the assistant doesn't seem to find them:
- Check that documents are processed. After uploading to the Knowledge Base, documents need time to be indexed. Look for a "Ready" status before expecting the assistant to use them.
- Verify knowledge sources are connected. Go to Assistant > Settings > Knowledge and confirm the relevant collections are enabled.
- Try rephrasing your question. The assistant searches by meaning, not keywords. If "What's our refund policy?" doesn't work, try "What does the handbook say about refunds?"
"Responses are slow"
The assistant's response time depends on a few factors:
- Large documents take longer to search through. If you've connected a very large knowledge base, complex queries naturally require more processing time.
- Deep search is more thorough but slower. For questions that span multiple documents, the assistant cross-references content before responding.
- Try simpler queries first. Break complex questions into smaller parts. Ask "What are the key dates in the contract?" before asking "Analyze the contract and compare it with last year's terms."
"Scheduled tasks aren't running"
If your cron jobs aren't firing as expected:
- Check the schedule. Go to Assistant > Settings > Crons and verify the timing is set correctly. Make sure the timezone matches your location.
- Review the task description. If the assistant doesn't have clear enough instructions, the task may silently fail. Try making the prompt more explicit.
- Check notifications. Results might be arriving in a delivery channel you're not monitoring. Verify whether results are sent to chat, notifications, or email.
If none of these solutions help, reach out to support through the Help section. Include details about what you expected to happen and what happened instead — it helps us resolve things faster.