Simultaneous Generation Lock
To ensure fair access across our rendering clusters, DigitalXLR enforces an active concurrency limit of one active generation task per account at a time.
Why HTTP 429 Occurs
If you submit a new generation request while a previous task is currently rendering, the system returns an HTTP 429 (Too Many Requests) notice:
"You already have a generation in progress. Please wait for your current generation to finish before starting a new one."Background Delayed Task Release
If a complex generation task remains on the GPU rendering cluster longer than expected, DigitalXLR automatically transitions the task status to delayed in the background.
- Lock Release: Once marked as delayed, your account's active-generation lock is automatically released.
- Submitting Additional Requests: You can submit a new generation while your delayed background task continues rendering to completion.