Queue [Default] at or near capacity

24x7 (multiplatform edition) just started having this problem. It must have been something I did but I can't figure out what it is.
This installation was solid and dependable until 8 days ago.

The scheduler is saying that the default queue is near capacity. (see snip below).

What can I do to resolve this?

[b]0-Dec-2017 12:00:05 AM 2 null null 24x7 Scheduler 24x7 Scheduler starting...
20-Dec-2017 12:10:15 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 205 GSM930 Load QPulse ToolId Semaphore file(s) \\cimaprod1\prod\foreignload\toolid\in\QPulseTools.tab is found. Submitting job to the queue.
20-Dec-2017 12:10:15 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 205 GSM930 Load QPulse ToolId Job started.
20-Dec-2017 12:10:27 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 205 GSM930 Load QPulse ToolId Job finished.
20-Dec-2017 01:00:00 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 226 Alert Process GSM952 for Task Card Hours Alert Job started.
20-Dec-2017 01:00:00 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 238 CRP550 - Task Cards Job started.
20-Dec-2017 01:00:09 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 226 Alert Process GSM952 for Task Card Hours Alert Job finished.
20-Dec-2017 06:00:15 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 205 GSM930 Load QPulse ToolId Semaphore file(s) \\cimaprod1\prod\foreignload\toolid\in\QPulseTools.tab is found. Submitting job to the queue.
20-Dec-2017 06:06:00 AM 1 null null 24x7 Scheduler Queue [default] is near or at max-jobs capacity. Maximum allowed number of jobs: 1000. Number of currently queued jobs: 800.
[/b]

I think I might have an explanation. I noticed from the log that job CRP550 entered the queue and did not finish.
I think that job might have caused the problem.

Its possible that this job threw a dialog box error and is waiting for a response.

Would this cause this problem?

	Quote:
	Its possible that this job threw a dialog box error and is waiting for a response. Would this cause this problem?

Yes, that certainly would. It would block the queue and eventually lead to "is near or at max-jobs capacity". Perhaps you can set timeout for the job in question, and let the scheduler to terminate it it and free the queue if the job gets stuck somehow.

Also, you can change that job properties, assign it to a separate queue, and make the scheduler not to queue new instances of the job if any are already running or queued. This way other jobs will not be impacted, they will run in a different queue, and for this one it would be easier to monitor and troubleshoot too.

got it. thanks. will do as you suggest.