📌 Problem
One or more items in the Job Manager remain in a Queued or JobQueued state and do not transition to Running, InProgress, or Completed.
No processing logs are generated, and the job appears to wait indefinitely.
This article applies only to jobs that remain in a Queued / JobQueued state and have not yet started execution.
If a job has transitioned to InProgress but does not advance, use the job‑specific troubleshooting articles as different causes and resolutions apply.
🔍 Root Cause
Common causes include:
- Another Job Manager task is already running
- A previously canceled or failed job did not exit cleanly
- System, licensing, or environment conditions are preventing execution
- The Job Manager UI state is stale and out of sync
🧠 What is “Queued / JobQueued”?
The Job Manager controls background processing and limits how many jobs may execute concurrently on a machine. Jobs marked Queued or JobQueued are waiting for execution and have not yet started.
This state does not indicate job failure or data corruption. Processing logs are not created until the job begins running.
Job Manager queues are local to the machine on which the job was submitted.
Jobs will only execute on that machine and will not transfer to or be picked up by other systems, even if the same project is opened elsewhere.
Important: This article applies only to jobs that remain Queued / JobQueued. If a job has already transitioned to InProgress, refer to the job‑specific troubleshooting articles listed below.
✅ Probable Resolutions
Verify No Other Job Is Running
Open the Job Manager and confirm that no other job is marked Running or InProgress. If another job is active, allow it to complete before expecting queued jobs to start.
Restart LP360
Close LP360 completely and reopen it. This forces the Job Manager to reload its internal state and often clears stalled queues.
Retry or Recreate the Job
If the job remains queued after restarting LP360, use Retry Job (if available) or delete the job and resubmit it from the originating tool.
Restart the System
If jobs continue to remain queued across multiple LP360 sessions, reboot the system to ensure all background services are fully reset.
📚 Additional Notes
Queued jobs do not time out automatically and may remain in this state until execution conditions are met.
If a job transitions to InProgress but does not advance, this article no longer applies. Use the appropriate job‑specific troubleshooting article instead.
Force Parallel Execution is an advanced option intended for experienced users only.
Enabling parallel execution may lead to resource contention, reduced performance, or instability and is not recommended as a general troubleshooting step.
📬 Need Help?
If jobs remain queued after completing the steps above, please Contact Support and include your LP360 version, job type, and a screenshot of the Job Manager.
Comments
0 comments
Please sign in to leave a comment.