// STEPS
01
Wait a short moment and refresh Library to confirm the status is still queued.
02
If every new job stays queued, the background job service is likely not receiving or running events.
03
Check that the production Inngest app is active and synced to /api/inngest.
04
Confirm Vercel has INNGEST_EVENT_KEY, INNGEST_SIGNING_KEY, and the correct INNGEST_APP_ID.
05
After the service is fixed, start a new generation. Old queued jobs may need to be retried.
// SELLER TIPS
Queued is different from processing. Processing means the worker has started.
If only one job is slow but others work, it may just be a larger image job.
Library is the source of truth for whether a job finished, failed, or needs retrying.