Skip to content
Index Inspector

Troubleshooting

Troubleshooting

Section titled “Troubleshooting”

If you’re having trouble with Index Inspector, check the solutions below for common issues.

Bot is not responding

Section titled “Bot is not responding”
  1. Check Connection: Ensure you have an active internet connection and Telegram is working.
  2. Verify /start: Make sure you have sent the /start command in a private chat with the bot.
  3. Bot Status: Sometimes the bot may be undergoing maintenance. Check the bot’s bio for any status updates.

Command returns an error

Section titled “Command returns an error”
  • Check Syntax: Ensure you are using the correct parameters (e.g., /scan main 45 instead of just /scan).
  • Project ID: If you have multiple projects, ensure you are providing the correct Project ID. Use /project_list to verify.

Scan fails with “Repository Access Denied”

Section titled “Scan fails with “Repository Access Denied””
  • Private Repos: If your repository is private, ensure you have provided a Git URL with the necessary access tokens or that the bot’s public key has been added to your repo’s deploy keys.
  • URL Format: Double-check the Git URL in /update_project. It should usually look like https://github.com/user/repo.git.

”No Queries Found” during scan

Section titled “”No Queries Found” during scan”
  • Check Scan Paths: Ensure the Scan Paths you provided in the config form actually contain the files where your database logic lives (e.g., use app/models/ or src/lib/db/).
  • Supported Patterns: Index Inspector looks for standard SQL strings and common ORM patterns (Eloquent, TypeORM, Prisma). If you use a very custom query builder, we might not detect it yet.
Section titled “Form link is expired or not working”
  • Regenerate Link: Form links sent by /init or /update_project are temporary. If the link doesn’t work, simply run the command again to get a fresh one.
  • Browser Compatibility: Ensure you are using a modern browser (Chrome, Firefox, Safari).

Result Migration is empty

Section titled “Result Migration is empty”
  • No Recommendations: If the scan didn’t find any necessary optimizations, no migration file will be generated.
  • Database Config: Ensure you selected the correct Database and Framework in your project settings, as this dictates how the migration is built.