# Follow jobs in Queue

Track waiting and running jobs, preview finished results, and handle requests that need review without creating duplicates.

Source: https://muse4ai.lovable.app/docs/queue · Updated 2026-11-02

## Before you start

- Send a request from Studio, a batch, or a connected agent.
- Keep Muse4AI running while it processes work.

## 1. Find the job

Open Queue and identify the job by its thumbnail and prompt. Read its status before taking action: it may be waiting, running, finished, failed, cancelled, or awaiting review.

## 2. Preview a result

Hover over or focus a job to open its quick preview. Use this to recognize the result without opening each job's full details.

## 3. Open full details

Click the job to open its drawer. Check the prompt, result, files, and available actions. Open the finished file or its folder from here when those actions are available.

## 4. Handle review without resending

Do not resubmit a job marked as needing review. The app is unsure whether Muse received it. Inspect Muse history and use Import from Muse history if a matching result exists; this retrieves a result rather than creating another one.

## Check it worked

You can identify the job's current state, open its result, and avoid duplicate submissions when delivery is uncertain.

## If it doesn't work

### Why does a job stay in the waiting state?

Check account readiness, usage limit, proxy health, and parallel-job availability. A paused batch can also keep its unsent jobs waiting.

### Is a job needing review the same as a failed job?

No. Muse may already have received it. Do not use a fresh Studio request or another job to repeat it; inspect the original job and Muse history first.

### Why are retry actions different between jobs?

Available actions depend on the job's state and whether the app knows Muse received it. Resolve the displayed cause instead of assuming every job is safe to resend.