Skip to main content

Impact of Other Jobs on a Scheduled Project Deletion

The following describes how the scheduling of a project deletion can be impacted by other Code Insight jobs.

Multiple Project Deletions Triggered​

When multiple project deletions have been triggered simultaneously, the first deletion triggered is in the Active state in the Jobs queue. The remaining deletions are placed in the Scheduled state and are run based on the scheduled order.

Electronic Update or Library Refresh in Progress​

If a deletion job is already scheduled when a Library Refresh or Electronic Update is added to the queue, the Library Refresh or Electronic Update will run first (once any already active jobs finish). The deletion job remains in a Scheduled state and will run according to queue order once the refresh or update is complete. (A Library Refresh and Electronic Update have priority over all other scheduled jobs.)

Scan Running on the Same Project​

A project deletion task cannot run on a project currently being scanned.

  • When you attempt to trigger the deletion from the project’s Summary page, the Manage Project > Delete Project option is disabled.
  • If you trigger the deletion from the project’s right-click menu in the Projects view, the deletion job is added to the Jobs queue. However, its final status shows as Failed , and the Error column for the job states “You cannot delete this project or scan folder while there are tasks scheduled or active for the project”.

Once the scan or rescan is complete, you can re-trigger the deletion task.