Looking for advice on handling transient 503 Service Unavailable errors when fetching screen recordings via the /api/v2/recordings/screen endpoint. Our AppFoundry integration processes high-volume compliance audits requiring sequential GET requests, but the pipeline fails after approximately 200 calls. Retries with exponential backoff mitigate the issue temporarily, yet the pattern suggests a server-side throttling mechanism distinct from standard rate limits. Is there a documented best practice for batching these requests or a specific header to signal bulk intent?