What are the procedures to perform when uploading/publishing a newer version of the package to Orchestrator is getting faulted with an error -"Modifying this process is not possible at the moment, because there are active jobs associated with it. (#1666) " ?
For Orchestrator version 2018.3 & 2018.4: This issue generally occurs when a job associated with the package is already running and the below parameter is not added in the web.config. file.
"Processes.AllowUpdateWithRunningJobs" parameter Specifies whether it is possible to update a process while having a running or pending jobs associated with it. Note that this parameter is hidden by default.
The following values are available:
- True - Processes can be modified while having associated running or pending jobs. Concerning this, there are a couple of things to consider:
- Running jobs associated with a modified process use the initial version of the process. The updated version is used for newly created jobs or at the next trigger of the same job.
- Pending jobs associated with a modified process use the updated version.
- False - Processes cannot be modified while having associated running or pending jobs. Trying to modify a process, in this case, displays the following error message: "Modifying this process is not possible at the moment, because there are active jobs associated with it. (#1666)". This is the default value.
For example, if the processes are to updated while having any associated jobs running, add <add key="Processes.AllowUpdateWithRunningJobs" value="True" /> in the web.config file. Read more on the Deployment procedure.
For Orchestrator version 2019 and above:
The same parameter is modified to specify whether it is possible to delete a process while having a running or pending jobs associated with it. Read more on the Web.Config setting file
- When checking for currently pending/running jobs, ensure to check the filter at the top of the page. By default, this filter only shows the "Last Day" of jobs.
- In any case, if pending/running jobs do not exist and still get this error try checking the same in SQL Database.
Create SQL query to identify the terminating state job. The following is the list of state code used in the dbo.jobs table:
The following query can be handy:
Select * from [UiPath].[dbo].[Jobs] where Jobs.State=3
Then update the terminating state to faulted, so that the terminating state is changed to faulted.
Update [UiPath].[dbo].[Jobs] set jobs.state=4 where Jobs.State=3 .