Troubleshooting
Practical steps for the issues people run into most often while using Verics. Work through the suggestions in order, and reach out if they do not resolve the problem.
Responses
A response stopped early or looks incomplete.
Possible cause: Very long conversations and large attachments add up, and each model can only take in a limited amount of text at once.
What to try
- Send the message again, or use the regenerate option to retry.
- Choose a model with a larger context window if one is available in your configuration.
- Lower the per-chat context limit or reduce the amount of attached content, then try again.
When to contact support: If responses keep stopping early on short messages with no attachments, contact support.
A response is in the wrong language.
Possible cause: The model follows the language it detects in your prompt and the conversation.
What to try
- Write your request in the language you want the answer in.
- Add a short instruction such as asking for the reply in a specific language.
When to contact support: If the language still does not match your request, contact support.
Files & attachments
A file upload was not accepted.
Possible cause: Uploads support common document and image types up to a size limit, so other formats or very large files are declined.
What to try
- Use a supported file type such as an image, PDF, Word document, plain text, or an email file.
- If the file is too large, reduce its size or split it into smaller parts.
- For design or other unsupported formats, export the content to a supported type such as PDF or an image first.
When to contact support: If a supported file within the size limit is still rejected, contact support.
An image upload failed.
Possible cause: The image may be too large or in a format that is not supported.
What to try
- Use a common image format such as PNG or JPG.
- Reduce the image size if it is very large, then upload it again.
When to contact support: If a standard image still fails to upload, contact support.
Input & models
Voice input isn't working.
Possible cause: Voice input needs permission to use your microphone in the browser.
What to try
- Allow microphone access when your browser asks for it.
- Check that the site is not blocked from using the microphone in your browser settings.
- Make sure no other application is currently using the microphone.
When to contact support: If the microphone is allowed but voice input still does not respond, contact support.
A model I want to use is not available.
Possible cause: Which models you can select can depend on your account configuration and any API keys set up for it.
What to try
- Choose another available model for your task.
- Check your settings to confirm which models are enabled for your configuration.
When to contact support: If a model you expect to have access to is missing, contact support.
Still stuck? Our team can help you work through it.