> ## Documentation Index > Fetch the complete documentation index at: https://docs.helloleo.dev/llms.txt > Use this file to discover all available pages before exploring further. # Common Issues > Solutions to frequently encountered problems Here are solutions to the most common issues you might encounter when using HelloLeo. ## Integration Issues ### Integration Not Connecting **Symptoms:** * Integration test fails * "Connection failed" error message * API calls return 401 or 403 errors **Solutions:** 1. **Verify credentials** - Double-check your API keys, tokens, and connection details 2. **Check permissions** - Ensure your API key has the necessary permissions (read/write) 3. **Test connection** - Use the "Test Connection" button in integration settings 4. **Review documentation** - Check the specific integration guide for requirements 5. **Check network** - Verify your network allows connections to the integration's API ### Integration Data Not Showing **Symptoms:** * Integration connects successfully but no data appears * Empty lists or tables * "No data found" messages **Solutions:** 1. **Check filters** - Review any filters or search criteria you've applied 2. **Verify permissions** - Ensure your API key has read access to the data 3. **Check data exists** - Verify the data exists in your integration account 4. **Review API limits** - Some integrations have rate limits or pagination requirements 5. **Check field names** - Ensure field/column names match exactly (case-sensitive) ### Can't Save Data to Integration **Symptoms:** * Create/update operations fail * "Permission denied" errors * Data doesn't appear after saving **Solutions:** 1. **Write permissions** - Ensure your API key has write/create permissions 2. **Required fields** - Check that all required fields are provided 3. **Data format** - Verify data types match the integration's expected format 4. **Validation rules** - Review any validation rules in your integration 5. **Check logs** - Use the Network Monitor to see detailed error messages ## Project Issues ### Project Not Building **Symptoms:** * Build fails with errors * Deployment stuck in "building" state * Error messages in build logs **Solutions:** 1. **Check dependencies** - Verify all required packages are installed 2. **Review errors** - Read the error messages carefully for specific issues 3. **Check code syntax** - Look for syntax errors in your code 4. **Clear cache** - Try refreshing or clearing the build cache 5. **Share with Leo** - Use "Share with Leo" to get debugging help ### Live Preview Not Working **Symptoms:** * Preview doesn't load * Blank screen in preview * Errors in preview console **Solutions:** 1. **Check browser console** - Open browser dev tools to see JavaScript errors 2. **Review network tab** - Check for failed API requests 3. **Verify routes** - Ensure your routes are correctly configured 4. **Check dependencies** - Verify all imports and dependencies are correct 5. **Refresh preview** - Try refreshing the preview iframe ### Code Changes Not Reflecting **Symptoms:** * Changes don't appear after saving * Old code still running * Preview shows outdated content **Solutions:** 1. **Save files** - Ensure all files are saved 2. **Refresh preview** - Manually refresh the preview 3. **Check build status** - Verify the project has finished building 4. **Clear cache** - Clear browser cache and reload 5. **Check file paths** - Verify you're editing the correct files ## Prompting Issues ### Leo Not Understanding Request **Symptoms:** * Leo creates something different than requested * Missing features or functionality * Incorrect implementation **Solutions:** 1. **Be specific** - Provide detailed descriptions of what you want 2. **Break down tasks** - Split complex requests into smaller steps 3. **Provide examples** - Include examples or references when possible 4. **Mention integrations** - Always specify which integration to use 5. **Clarify requirements** - Add more context about your use case ### Leo Creates Wrong Code **Symptoms:** * Code doesn't match your tech stack * Wrong framework or library used * Incompatible code patterns **Solutions:** 1. **Specify tech stack** - Mention your preferred frameworks/libraries 2. **Provide context** - Share existing code patterns you want to follow 3. **Request fixes** - Ask Leo to fix specific issues 4. **Iterate** - Refine your prompts based on results 5. **Use examples** - Reference similar working code ### Integration Not Used Correctly **Symptoms:** * Leo doesn't use the integration you specified * Wrong API endpoints called * Incorrect data format **Solutions:** 1. **Explicitly mention integration** - Always say "from \[Integration]" or "to \[Integration]" 2. **Specify endpoints** - Mention specific API endpoints if needed 3. **Provide data structure** - Describe the expected data format 4. **Check integration docs** - Review the integration documentation 5. **Test connection** - Verify the integration is properly configured ## Performance Issues ### Slow Response Times **Symptoms:** * Leo takes long time to respond * Builds take too long * Preview loads slowly **Solutions:** 1. **Check project size** - Large projects may take longer to process 2. **Simplify requests** - Break complex requests into smaller parts 3. **Review dependencies** - Too many dependencies can slow builds 4. **Check network** - Verify your internet connection is stable 5. **Wait for completion** - Some operations naturally take time ### High Credit Usage **Symptoms:** * Credits depleting quickly * Unexpected credit charges **Solutions:** 1. **Review credit costs** - Check what operations consume credits 2. **Optimize prompts** - More efficient prompts use fewer credits 3. **Avoid unnecessary rebuilds** - Only rebuild when needed 4. **Monitor usage** - Track your credit usage in account settings 5. **Use preview** - Test in preview before deploying ## Getting Help If you're still experiencing issues: 1. **Share with Leo** - Use the "Share with Leo" feature to get debugging help 2. **Check Network Monitor** - Review API calls and errors 3. **Review Documentation** - Check relevant documentation pages 4. **Contact Support** - Join our [Discord community](https://discord.gg/RBJnhMa8p6) 5. **Report Issues** - Report bugs or issues through support channels Learn debugging techniques Find support resources