since the update to v23.3, the execution of all kinds of jobs is blocked as soon as another job is running - also if they operate on totally different security systems.
Is this a defect or new for v23.3? In the release notes, there have been some changes to the job mangement, but not regarding jobs running for different security systems.
Thank you for the feedback!
Solved! Go to Solution.
Can you provide more details on the jobs that are stuck? There are updates to job execution from v23.1 onwards. Please refer below link for Best practices for Job Scheduling for your reference:
thank you for the quick response!
The conflicting jobs in our instance are of the type "Application Data Import (Single Threaded)" and target different security systems.
In the referred link it is only stated that: "Application Data Import (Multi Threaded) and Application Data Import (Single Threaded) are also conflicting in nature if associated to the same security system."
That is why the question arised whether there is a bug in our instance.
short update on this entry: Having no jobs of the type "Application Data Import (Single Threaded)" running in parallel is actually wanted behaviour also for different security systems.
The job popup shows a wrongful message which is going to be changed in a future release: