Skip to main contentTroubleshooting
Common issues and solutions when working with the Voyager API.
Authentication Issues
Invalid Credentials
Error: 401 Unauthorized
Solutions:
- Verify your email and password
- Check that API access is enabled for your account
- Ensure you’re using the correct API base URL
Token Expired
Error: 401 Unauthorized with “Invalid token”
Solutions:
- Re-authenticate to get a new token
- Implement token refresh logic
- Check token expiration time
Export Issues
Export Fails
Error: 403 Forbidden or export never completes
Solutions:
- Verify you have
PROJECT_DATA_EXPORT capability
- Check that the project exists and is accessible
- Ensure the project has completed processing
- Check export status endpoint for error details
Export Takes Too Long
Issue: Export generation takes hours
Solutions:
- Large projects can take 30+ minutes to export
- Use data views for quick analysis instead
- Export specific data types only (meshes, volumes, etc.)
- Check export status periodically rather than waiting
Data Access Issues
Project Not Found
Error: 404 Not Found
Solutions:
- Verify the project ID is correct
- Check that you have access to the project
- Ensure the project hasn’t been deleted
- Verify workspace permissions
No Data Available
Issue: Project exists but has no data objects
Solutions:
- Ensure scan processing has completed
- Check project status endpoint
- Verify data objects exist in project document
Analysis Issues
Analysis Fails to Start
Error: 400 Bad Request or 403 Forbidden
Solutions:
- Verify project is in correct state (ready for analysis)
- Check that required capabilities are enabled
- Ensure project has necessary data (e.g., volume for mesh generation)
Analysis Never Completes
Issue: Analysis stays in “processing” state
Solutions:
- Large analyses can take hours
- Check project status endpoint for details
- Verify project hasn’t been modified during analysis
- Contact support if analysis is stuck for >24 hours
Network Issues
Connection Timeout
Error: requests.exceptions.Timeout
Solutions:
- Check your internet connection
- Verify firewall settings
- Try from a different network
- Increase timeout values for large operations
SSL Certificate Errors
Error: SSL verification failed
Solutions:
- Ensure you’re using HTTPS
- Check system clock is correct
- Verify certificate chain (rare issue)
Rate Limiting
Too Many Requests
Error: 429 Too Many Requests
Solutions:
- Implement exponential backoff
- Add delays between requests
- Reduce request frequency
- Contact support for higher limits
Getting Help
Support Resources
- Email: support@lumafield.com
- Documentation: Check relevant guides and API reference
- Error Messages: Read error details carefully
When contacting support, include:
- API endpoint you’re calling
- Request/response details (sanitize credentials)
- Error messages and status codes
- Steps to reproduce the issue
Next Steps
