My app times out when media generation takes too long, and I need an asynchronous task workflow instead.

Introduce an asynchronous task workflow for media generation so long-running jobs don’t cause request timeouts. Users can start a generation job, continue using the app, and retrieve results when processing completes.

This feature replaces long-running, timeout-prone media generation requests with an asynchronous job workflow. Instead of waiting for media generation to finish in a single request, the app creates a background task and immediately returns a job identifier. The client can then check the job’s status later and fetch the generated media once it is ready. This approach prevents server or client timeouts when media generation takes longer than typical HTTP request limits. It also improves the user experience by keeping the UI responsive and allowing users to navigate away while processing continues. The workflow supports clearer progress communication by exposing states such as queued, running, completed, and failed. It makes failures easier to handle by separating job execution from the original request and enabling retries or follow-up actions. This design scales better under load because media generation can be managed and scheduled independently of user-facing requests. It is especially useful for compute-heavy media generation, peak-traffic periods, or environments with strict gateway timeout limits.