Troubleshooting
Diagnose and resolve common configuration issues to ensure optimal performance and reliability of your Probably setup.
API Key Issues
Section titled “API Key Issues”Common API Key Problems
Section titled “Common API Key Problems”Invalid or Expired Keys
- Symptoms: Authentication errors, “invalid API key” messages
- Causes: Incorrect key format, expired subscription, revoked access
- Solutions:
- Verify key format matches provider requirements
- Check account status on provider dashboard
- Generate new API key if expired
- Ensure proper key copying (no extra spaces)
Rate Limiting Issues
- Symptoms: Slow responses, “rate limit exceeded” errors
- Causes: High usage with single provider, insufficient rate limits
- Solutions:
- Add API keys from additional providers
- Upgrade to higher-tier plans with provider
- Spread usage across multiple accounts
- Wait for rate limits to reset
Permission Errors
- Symptoms: “Insufficient permissions” or access denied errors
- Causes: API key lacks required permissions, account restrictions
- Solutions:
- Verify API key has full access permissions
- Check account billing and payment status
- Review provider-specific permission settings
- Contact provider support for access issues
API Key Validation Steps
Section titled “API Key Validation Steps”✅ Working API Key
- Instant response to test queries
- No authentication errors
- Full access to model capabilities
- Consistent performance
❌ Problematic API Key
- Error messages on requests
- Slow or failed responses
- Limited functionality access
- Inconsistent behavior
Testing API Keys
Section titled “Testing API Keys”Manual Verification
- Remove Key: Temporarily remove the problematic key
- Test Functionality: Try analysis without the key
- Re-add Key: Add the key back and test again
- Compare Performance: Note any differences in behavior
Provider Dashboard Check
- Usage Metrics: Check recent API usage on provider dashboard
- Billing Status: Verify account is in good standing
- Key Status: Confirm key is active and not revoked
- Rate Limits: Review current usage against limits
Database Connection Issues
Section titled “Database Connection Issues”Connection Failures
Section titled “Connection Failures”Network Connectivity
- Symptoms: Connection timeout, “cannot reach host” errors
- Causes: Network issues, firewall blocking, wrong host/port
- Solutions:
- Verify host address and port number
- Check firewall and VPN settings
- Test network connectivity to database server
- Confirm database server is running
Authentication Problems
- Symptoms: “Access denied”, authentication failure messages
- Causes: Wrong credentials, expired passwords, permission issues
- Solutions:
- Verify username and password are correct
- Check if password has expired or changed
- Confirm user has database access permissions
- Test credentials using database client tools
SSL/TLS Configuration
- Symptoms: SSL handshake failures, certificate errors
- Causes: SSL mode mismatch, certificate issues, security settings
- Solutions:
- Try different SSL modes (require, prefer, disable)
- Verify certificate validity and trust chain
- Check database SSL configuration
- Update SSL settings in connection config
Database-Specific Issues
Section titled “Database-Specific Issues”Snowflake Connection Problems
- Account Identifier: Ensure correct format (account.region.cloud)
- Role and Warehouse: Verify user has access to specified role/warehouse
- Network Policy: Check if IP restrictions apply
- MFA Requirements: Handle multi-factor authentication if enabled
Performance Issues
Section titled “Performance Issues”Slow Analysis Performance
Section titled “Slow Analysis Performance”System Resource Constraints
- Symptoms: Slow responses, system lag, memory errors
- Causes: Insufficient RAM, CPU bottlenecks, disk space issues
- Solutions:
- Close unnecessary applications
- Increase system memory if possible
- Use data sampling for large datasets
- Clear temporary files and caches
Network Performance Issues
- Symptoms: Slow data loading, timeouts during analysis
- Causes: Slow internet connection, database network latency
- Solutions:
- Test internet connection speed
- Use local data sources when possible
- Optimize database queries for performance
- Consider database connection pooling
Configuration Optimization
- Single Provider Limitation: Add multiple API keys for better performance
- Inefficient Queries: Optimize database queries and indexing
- Large Dataset Handling: Use appropriate sampling and filtering
- Resource Allocation: Adjust system resource allocation
Memory and Resource Issues
Section titled “Memory and Resource Issues”Memory Management
- Large Dataset Loading: Use sampling or chunked processing
- Memory Leaks: Restart application if memory usage grows continuously
- Cache Management: Clear caches if memory usage is high
- Resource Monitoring: Monitor system resource usage patterns
Disk Space Issues
- Cache Storage: Clear application caches if disk space is low
- Temporary Files: Clean up temporary analysis files
- Data Storage: Move large datasets to external storage
- Log Files: Archive or delete old log files
Error Messages and Solutions
Section titled “Error Messages and Solutions”Common Error Categories
Section titled “Common Error Categories”Authentication Errors
"Invalid API key" → Check key format and account status"Unauthorized access" → Verify account permissions and billing"Rate limit exceeded" → Add more API keys or wait for resetConnection Errors
"Connection timeout" → Check network and firewall settings"Host not found" → Verify database host address"Access denied" → Check database credentials and permissionsSystem Errors
"Out of memory" → Close applications or increase system memory"Disk space full" → Clear caches and temporary files"Process timeout" → Reduce dataset size or optimize queriesDiagnostic Steps
Section titled “Diagnostic Steps”Step-by-Step Troubleshooting
- Identify Error Type: Determine if it’s API, database, or system related
- Check Logs: Review any available error logs or messages
- Isolate Issue: Test individual components separately
- Verify Configuration: Double-check all settings and credentials
- Test Connectivity: Verify network and service availability
- Apply Solutions: Implement appropriate fixes based on diagnosis
System Health Check
- API Keys: Test each provider key individually
- Database Connections: Verify all configured connections
- System Resources: Check memory, disk, and CPU usage
- Network Connectivity: Test internet and database connectivity
Configuration Recovery
Section titled “Configuration Recovery”Manual Settings Management
Section titled “Manual Settings Management”Document Your Configuration
- Record API Keys: Maintain secure record of working API keys
- Connection Details: Note database connection parameters that work
- Settings Notes: Document any configuration changes made
Recovery Process
- Clear Settings: Remove problematic configuration manually
- Re-enter Settings: Add API keys and connections back individually
- Test Incrementally: Verify each setting works before adding the next
- Verify Functionality: Ensure each component works properly
Fresh Installation Setup
Section titled “Fresh Installation Setup”Clean Configuration
- Remove All Settings: Clear existing configuration
- Start with Basics: Add one API key first
- Test Functionality: Verify basic operation works
- Add Incrementally: Add additional keys and connections
- Monitor Performance: Watch for issues as you add components
Best Practices for New Setup
- Start with single API key and test thoroughly
- Add one database connection at a time
- Monitor performance after each addition
- Document working configuration for future reference
Performance Optimization Checklist
Section titled “Performance Optimization Checklist”Essential Optimizations
Section titled “Essential Optimizations”API Configuration
- Multiple AI provider API keys configured
- Keys tested and verified working
- Billing status confirmed for all providers
- Rate limits understood and monitored
Database Optimization
- Connection parameters optimized
- SSL settings configured properly
- Query timeouts set appropriately
- Connection pooling enabled where applicable
System Configuration
- Adequate system memory available
- Fast storage (SSD) for better performance
- Stable network connection verified
- Background applications minimized
Advanced Troubleshooting
Section titled “Advanced Troubleshooting”Manual Performance Monitoring
- Observe response times during analysis
- Monitor system resource usage through OS tools
- Note any patterns in slow performance
- Adjust dataset sizes and complexity based on performance
Preventive Maintenance
- Regularly update API keys before expiration
- Monitor provider account status and billing
- Test database connections periodically
- Keep system resources optimized
What’s Next?
Section titled “What’s Next?”Performance Optimization
Learn advanced techniques to optimize your system performance and configuration.
PXL Language
Explore the PXL language for advanced data analysis and custom operations.