I can’t tell which generation requests should be synchronous versus handled as background jobs in my product.

This feature helps you decide whether a generation request should run synchronously (immediate response) or asynchronously as a background job. It provides clear guidance to improve user experience, system reliability, and performance under varying workloads.

This feature clarifies when generation requests should be processed synchronously versus queued and handled in the background. It helps you evaluate requests based on expected latency, payload size, computational cost, and user interaction patterns. For fast, lightweight generations that users expect instantly, it recommends synchronous handling to keep flows responsive. For longer-running or resource-intensive generations, it recommends background jobs to prevent timeouts and keep your app stable. The feature supports designing consistent UX patterns such as progress indicators, job status polling, and notifications for completed results. It also helps you plan for traffic spikes by routing heavy work through queues and workers rather than tying up web threads. By making this decision process explicit, teams can standardize implementation across endpoints and avoid ad-hoc handling. It reduces the risk of poor user experiences caused by long waits, failed requests, or unpredictable response times. The result is a more scalable architecture that aligns performance characteristics with user expectations.