Changing an object's "Allow simultaneous executions" setting from a fixed limit to unlimited while tasks are already queued causes the previously-queued tasks to remain in status WAITING (PARALLEL TASK) indefinitely, even when no other instance of that object is active.
Expected: once nothing else is blocking them, previously-waiting tasks should be able to proceed.
Actual: pre-existing waiting tasks never resume - only tasks generated after the setting change run normally under the new limit.
Release: v24.x 26.x
Component: Automation Engine
Workaround:
Filter the tasks stuck in WAITING (PARALLEL TASK) status via process monitoring & Cancel the stuck instances.
Relaunch the jobs; the new instances will correctly pick up the updated unlimited setting.
Solution:
Update to a fix version listed below or a newer version if available.
Fix version:
Component(s): Automation Engine
Automation.Engine TBA - TBA