- Environment: Europe/London
- Endpoint:
/api/v2/analytics/bulk-data/export-jobs - Scope: Digital Channel (Chat/Web Messenger)
- Issue: HTTP 429 Too Many Requests
Why does this setting trigger a rate limit when fetching metadata for a legal hold export?
The bulk export job initiates correctly, but the subsequent polling for job status and metadata retrieval fails repeatedly with 429 errors. The payload specifies view: FULL and includes the necessary legal_hold flags. The request rate is well below the documented limit for standard users, but the system treats the metadata fetch as a separate high-frequency call.
The error response indicates retry-after: 60, which disrupts the automated chain of custody process. The job times out before completion because the retry logic in our script does not handle the exponential backoff correctly for this specific endpoint.
Is there a specific header or parameter to bundle the metadata request with the initial export job to avoid this separation? The current behavior makes it impossible to maintain a continuous audit trail for the discovery request. The S3 bucket permissions are verified, and the IAM role has full access. This issue only appears for digital channels, not voice recordings.