Error Messages & Solutions

Troubleshooting

Common error messages you might encounter and how to resolve them.

Quick Error Lookup

Use Ctrl+F (Cmd+F on Mac) to quickly search for specific error messages on this page. Copy the exact error text for the best results.

Connection Errors

"Permission denied: Missing or insufficient permissions"

Possible Causes:

  • • Admin SDK service account lacks proper IAM roles
  • • Firestore security rules are too restrictive
  • • Service account was disabled or deleted

Solutions:

  1. 1. Verify your service account has "Cloud Datastore User" role
  2. 2. Check Firestore security rules allow server-side access
  3. 3. Ensure the service account is active in Firebase Console
  4. 4. Try regenerating the service account key
"Project not found or insufficient permissions"

Possible Causes:

  • • Incorrect project ID in service account JSON
  • • Project was deleted or moved
  • • Billing account issues

Solutions:

  1. 1. Double-check the project_id field in your service account JSON
  2. 2. Verify the project exists in Firebase Console
  3. 3. Ensure Firestore is enabled for the project
  4. 4. Check that billing is set up if required
"Invalid service account credentials"

Possible Causes:

  • • Malformed private key in manual entry
  • • Corrupted JSON file
  • • Expired or revoked service account key

Solutions:

  1. 1. Re-download the service account JSON from Firebase
  2. 2. Ensure private key includes full content with headers/footers
  3. 3. Try uploading JSON file instead of manual entry
  4. 4. Generate a new service account key if the issue persists
Correct Private Key Formattext
-----BEGIN PRIVATE KEY-----
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQC...
...rest of key content...
-----END PRIVATE KEY-----

Schema Analysis Errors

"Failed to analyze collection: timeout"

Possible Causes:

  • • Collection has very large documents
  • • Network connectivity issues
  • • High server load

Solutions:

  1. 1. Try analyzing fewer collections at once
  2. 2. Check your internet connection
  3. 3. Retry the analysis after a few minutes
  4. 4. Contact support if the issue persists
"No documents found in collection"

Possible Causes:

  • • Collection is genuinely empty
  • • Security rules prevent document access
  • • Documents exist in subcollections only

Solutions:

  1. 1. Verify the collection has documents in Firebase Console
  2. 2. Check if documents are in subcollections
  3. 3. Review Firestore security rules
  4. 4. Ensure service account has read access
"Schema generation failed: invalid document structure"

Possible Causes:

  • • Documents contain unsupported data types
  • • Extremely nested object structures
  • • Circular references in document data

Solutions:

  1. 1. Check for extremely deep nesting (20+ levels)
  2. 2. Look for circular references in your data
  3. 3. Try with a different collection first
  4. 4. Report the issue with collection details

AI Analysis Errors

"AI analysis not available"

Possible Causes:

  • • Trial period has expired
  • • No active Pro subscription
  • • AI service temporarily unavailable

Solutions:

  1. 1. Check your subscription status in dashboard
  2. 2. Upgrade to Pro plan if trial expired
  3. 3. Wait a few minutes and try again
  4. 4. Contact support if the issue persists
"AI analysis timeout"

Possible Causes:

  • • Too many collections selected for analysis
  • • Large sample size with complex data
  • • High server load

Solutions:

  1. 1. Reduce number of selected collections (try 3-5)
  2. 2. Decrease sample size to 20-50 documents
  3. 3. Use "Shallow" analysis depth
  4. 4. Retry the analysis later
"Insufficient data for AI analysis"

Possible Causes:

  • • Collections have too few documents
  • • Documents lack meaningful field relationships
  • • Selected collections are unrelated

Solutions:

  1. 1. Ensure each collection has at least 10 documents
  2. 2. Select collections that are likely related
  3. 3. Increase sample size if collections are large
  4. 4. Try with different collection combinations

Data Browsing Errors

"Search failed: invalid query"

Possible Causes:

  • • Special characters in search value
  • • Field doesn't exist or has different type
  • • Firestore query limitations

Solutions:

  1. 1. Try simpler search terms without special characters
  2. 2. Verify the field exists in the collection
  3. 3. Use exact field names (case-sensitive)
  4. 4. Try browsing without search filters first
"Pagination error: invalid cursor"

Possible Causes:

  • • Collection data changed during browsing
  • • Network interruption during pagination
  • • Documents were deleted while browsing

Solutions:

  1. 1. Refresh the page and start browsing again
  2. 2. Clear any active search filters
  3. 3. Try a smaller page size
  4. 4. Ensure stable internet connection

Authentication Errors

"Session expired. Please sign in again."

Possible Causes:

  • • Firebase authentication token expired
  • • Browser session cleared
  • • Long period of inactivity

Solutions:

  1. 1. Sign out and sign back in
  2. 2. Refresh the page
  3. 3. Clear browser cache if issue persists
  4. 4. Check if your Google account is still active
"Failed to authenticate with Google"

Possible Causes:

  • • Pop-up blocked by browser
  • • Third-party cookies disabled
  • • Network/firewall restrictions

Solutions:

  1. 1. Enable pop-ups for this site
  2. 2. Enable third-party cookies temporarily
  3. 3. Try incognito/private browsing mode
  4. 4. Disable ad blockers temporarily
General Troubleshooting Steps

If you encounter an error not listed above, try these general troubleshooting steps:

Quick Fixes

  • 1. Refresh the page (F5 or Ctrl+R)
  • 2. Clear browser cache and cookies
  • 3. Try a different browser
  • 4. Check internet connection
  • 5. Sign out and sign back in

Getting Help

  • • Copy the full error message
  • • Note what you were doing when it occurred
  • • Include browser and OS information
  • • Email support with these details
  • • Check our status page for known issues