Authentication
”Invalid API key” Error
Problem: API requests return401 Unauthorized with “Invalid API key” message.
Solutions:
- Verify the API key is correct (check for typos or extra whitespace)
- Ensure the key hasn’t been deleted or revoked
- Check that you’re using the correct header format:
X-Avala-Api-Key - Confirm you’re sending the key as a header, not a query parameter
”API key has expired” Error
Problem: API returns401 Unauthorized with expired key message.
Solutions:
- Create a new API key in Mission Control under Settings
- Update your applications and environment variables with the new key
- Consider setting longer or no expiration for production keys
- Set up key rotation alerts to avoid unexpected expirations
”Permission denied” Error
Problem: API returns403 Forbidden when accessing a resource.
Solutions:
- Verify you have access to the requested dataset or project
- Check your organization membership and role (admin, manager, annotator)
- Ensure your API key has the required scopes for the operation
- Contact your organization admin to request access
API Issues
Rate Limiting (429 Too Many Requests)
Problem: API returns429 status code with rate limit errors.
Solutions:
- Implement exponential backoff in your retry logic
- Check the
Retry-Afterheader for the recommended wait time - Reduce the number of concurrent requests
- For bulk operations, use batch endpoints where available
Pagination Errors
Problem: Receiving empty results or unexpected data when paginating. Solutions:- Use cursor-based pagination instead of offset pagination
- Do not modify filters between pagination requests
- Pass the full
nextURL returned by the API rather than constructing it manually - Check that the
nextfield isnullto detect the last page
Request Timeout
Problem: API requests time out before completing. Solutions:- Increase your client timeout setting (recommended: 30 seconds for standard requests)
- For large exports or uploads, use a longer timeout (60-120 seconds)
- Check your network connection and firewall settings
- If specific endpoints consistently time out, contact support
Uploads
Upload Fails for Large Files
Problem: Uploads timeout or fail for large files. Solutions:- Check your network connection stability
- Use the SDK’s built-in upload methods, which handle chunked uploads automatically
- For files over 1 GB, ensure your client timeout is set to at least 120 seconds
- Try uploading during off-peak hours
- For very large datasets, consider splitting into smaller batches
”Invalid file format” Error
Problem: Upload rejected with format error. Solutions:- Verify the file is a supported format:
- Images: JPEG, PNG, WebP
- Videos: MP4, MOV
- Point clouds: PCD, PLY
- Sensor data: MCAP, ROS Bag
- Check that the file is not corrupted
- Ensure file extension matches actual content type
MCAP Parsing Errors
Problem: MCAP files fail to process after upload. Solutions:- Validate your MCAP file locally using the MCAP CLI
- Ensure all schemas referenced by channels exist in the file
- Check that timestamps are monotonically increasing within each channel
- Verify the file was not truncated during transfer
Datasets
Items Not Appearing
Problem: Uploaded items don’t show in the dataset. Solutions:- Check if processing is still in progress (look for the processing status indicator)
- Refresh the page or re-fetch via the API
- Verify the upload completed successfully by checking the upload response status
- Check that items match the dataset’s expected data type
”Dataset not found” Error
Problem: Can’t access a dataset that should exist. Solutions:- Verify you’re using the correct owner and slug format:
- Check dataset visibility (private datasets require explicit access)
- Confirm you have permission to view the dataset
- Ensure the dataset has not been deleted
Sequence Status Stuck
Problem: A sequence remains in “processing” status indefinitely. Solutions:- Wait up to 15 minutes for large sequences to finish processing
- Check that all referenced files in the sequence were uploaded successfully
- Verify the sequence data is in a supported format
- If stuck for more than 30 minutes, contact support with the sequence ID
Projects
Can’t Create Project
Problem: Project creation fails or returns an error. Solutions:- Ensure you have at least one dataset selected as the data source
- Verify you have permission to create projects in the organization (manager or admin role)
- Check that your label taxonomy is valid and does not contain duplicate label names
- Ensure the project name is unique within your organization
Annotations Not Saving
Problem: Annotations disappear after saving or the save action fails. Solutions:- Check your network connection for intermittent issues
- Verify you have edit permissions on the project
- Look for error messages in the browser console (F12)
- Ensure the task has not been reassigned or completed by another user
- Try refreshing the page and re-annotating
Task Assignment Issues
Problem: Tasks are not being assigned to annotators as expected. Solutions:- Verify annotators have been added to the project with the correct role
- Check that the work batch configuration is correct
- Ensure there are unassigned tasks available in the project
- Confirm the project status is active (paused projects do not assign new tasks)
Exports
Export Stuck in “Processing”
Problem: Export never completes and remains in processing status. Solutions:- Check that the project has completed annotations to export
- Try creating a smaller export by filtering by date or task status
- For large exports (10,000+ items), allow up to 30 minutes for processing
- Contact support if stuck for more than 1 hour
”Download URL expired” Error
Problem: Can’t download a completed export. Solutions:- Export download URLs expire after 7 days
- Create a new export to generate a fresh download URL
- Automate the download step in your pipeline to avoid expiration
Empty Export
Problem: Exported file contains no annotations or is empty. Solutions:- Verify the project has completed and accepted tasks
- Check that your export filters are not too restrictive
- Ensure annotations exist for the selected export format
- Try exporting without filters to confirm data exists
Mission Control
Viewer Not Loading
Problem: The annotation viewer shows a blank screen or loading spinner. Solutions:- Check the browser console for errors (F12 on most browsers)
- Try a different browser (Chrome or Firefox recommended)
- Clear browser cache and reload the page
- Verify the dataset item has completed processing
- Disable browser extensions that may interfere (ad blockers, privacy tools)
Slow Performance
Problem: Interface is slow or unresponsive. Solutions:- Close other browser tabs to free memory
- Use a modern browser with hardware acceleration enabled
- For large point clouds, reduce point density in the viewer settings
- Check your internet connection speed (minimum 10 Mbps recommended)
- Try zooming into a smaller area of the dataset
3D Viewer Issues
Problem: 3D point cloud or cuboid annotations are not rendering correctly. Solutions:- Ensure your browser supports WebGL 2.0
- Update your GPU drivers to the latest version
- Enable hardware acceleration in your browser settings
- Reduce the point cloud density if rendering is slow
- Try a different browser if rendering artifacts appear
MCP Integration
MCP Endpoint Not Responding
Problem: Requests to the MCP endpoint return errors. Solutions:- Verify you are sending requests to
POST /api/v1/mcp/with a valid API key - Ensure your API key has staff-level access (the MCP endpoint is currently staff-only)
- Check that the request body is valid JSON-RPC format
- Review the response body for specific error details
MCP Authentication Errors
Problem: MCP requests return authentication errors. Solutions:- Verify your
AVALA_API_KEYenvironment variable is set correctly - Ensure the API key has not expired or been revoked
- Confirm the API key has staff-level permissions (required for the MCP endpoint)
- Check that you are including the key in the
X-Avala-Api-Keyheader
Getting Help
If you are still stuck after trying the solutions above:- Search our documentation at docs.avala.ai
- Email support at support@avala.ai with details about the issue, including any error messages and steps to reproduce
- Visit our GitHub repository for SDK issues, bug reports, and feature requests
When contacting support, include the following information to help us resolve your issue faster: your organization slug, the API endpoint or page URL, the full error message, and the approximate time the issue occurred.