Limit the Number of Jobs Per Project

You can limit the number of concurrent jobs that are being processed by Intelligence Server for a project. If you have multiple projects on an Intelligence Server, each can have its own job limit setting. Limiting the number of concurrent jobs per project helps reduce unnecessary strain on the system by limiting the amount of resources that concurrently executing jobs can take up.

Concurrent jobs include report requests, element requests, and autoprompt requests that are executing or waiting to execute. Finished jobs that are still open, cached jobs, and jobs that returned an error are not counted. If the limit is reached, a user sees an error message stating that the number of jobs per project is too high. The user then needs to submit the job again.

In a clustered system, these settings limit the number of concurrent jobs per project on each node of the cluster.

To specify this job limit setting, in the Project Configuration Editor for the project, select the Governing Rules: Default: Jobs category, and specify the number of concurrent jobs that you want to allow for the project in each Jobs per project field. You can also specify a maximum number of interactive jobs (jobs executed by a direct user request) and scheduled jobs (jobs executed by a scheduled request). A value of -1 indicates that the number of jobs that can be executed has no limit.