Troubleshooting Center

This usually occurs when the underlying data pipeline experiences a timeout or schema mismatch. First, check your /status page for active incidents. If all systems are green, clear your browser cache and try a hard refresh (Ctrl+F5). If the issue persists, verify that your source database credentials haven't expired and that the ETL job isn't stuck in a retry loop.

Navigate to Settings → Security → API Keys. Click the three-dot menu next to the active key and select "Rotate Secret". Your old key will remain valid for 24 hours for a smooth transition. For immediate revocation, choose "Revoke Immediately".

Model drift typically happens when training data distributions shift over time. DataPulse automatically flags drift >5%, but you can force a retrain via the Model Registry UI. Check your feature stores for missing values or schema changes, and ensure your validation pipeline isn't leaking future data.

This indicates you've hit the rate limit for your plan. Standard limits are 1,000 requests/minute. Implement exponential backoff in your client code, or upgrade to a higher tier. You can monitor your quota usage in real-time via the X-RateLimit-Remaining header in API responses.

Exports exceeding 50,000 rows are processed asynchronously. Instead of waiting in the browser, use the "Scheduled Export" feature or query our REST API endpoint /v2/exports/{id} to poll for completion. Files are delivered via secure S3/Azure Blob links that expire in 48 hours.