When adding more tasks to a job with a JobManagerTask, it seems to me that those other tasks inherit the "AllowLowPriorityNode: false" flag I have set on the job manager

Question

When adding more tasks to a job with a JobManagerTask, it seems to me that those other tasks inherit the "AllowLowPriorityNode: false" flag I have set on the job manager

Håkon Lie 0

Has anyone else experienced this? I set "AllowLowPriorityNode: false" on my JobManagerTask, but when I create other tasks under the same job, they refuse to run on low priority nodes. The field is only available on the job manager task.

Jilakara Hemalatha 3,365 Reputation points Microsoft External Staff Moderator

2025-10-23T19:37:50.8733333+00:00
Hi Håkon Lie,

Thank you for reaching out and sharing your observation regarding the AllowLowPriorityNode setting on the Job Manager task.

We can confirm that the behavior you observed is expected.

The AllowLowPriorityNode setting applies only to the JobManagerTask. This flag is intended to prevent preemption of long-running Job Manager tasks by low-priority nodes.

Other tasks under the same job do not inherit this setting. There is currently no configuration on jobs or regular tasks that prevents them from running on available low-priority nodes.

Please let me know if you have any queries.
Jilakara Hemalatha 3,365 Reputation points Microsoft External Staff Moderator

2025-10-27T04:05:04.61+00:00

Hi Håkon Lie,

Could you please confirm that above provided information was resolved your query. Please let us know if you have any questions.
Håkon Lie 0 Reputation points

2025-10-27T07:14:29.28+00:00

Hi..
"We can confirm that the behavior you observed is expected."
"The AllowLowPriorityNode setting applies only to the JobManagerTask. This flag is intended to prevent preemption of long-running Job Manager tasks by low-priority nodes."

This is not the behiavor I observed. You must not have read my ticket at all? As this is in the title: "it seems to me that those other tasks inherit the "AllowLowPriorityNode: false" flag I have set on the job manager".

The behavior I observed is that other tasks added after the jobmanagertask does NOT run on lowpiority nodes when the flag is set to false on the jobmanager task

1 answer

Your answer

Jilakara Hemalatha 3,365 Reputation points Microsoft External Staff Moderator

2025-10-23T19:37:50.8733333+00:00

Hi Håkon Lie,

Thank you for reaching out and sharing your observation regarding the AllowLowPriorityNode setting on the Job Manager task.

We can confirm that the behavior you observed is expected.

The AllowLowPriorityNode setting applies only to the JobManagerTask. This flag is intended to prevent preemption of long-running Job Manager tasks by low-priority nodes.

Other tasks under the same job do not inherit this setting. There is currently no configuration on jobs or regular tasks that prevents them from running on available low-priority nodes.

Please let me know if you have any queries.
Jilakara Hemalatha 3,365 Reputation points Microsoft External Staff Moderator

2025-10-27T04:05:04.61+00:00

Hi Håkon Lie,

Could you please confirm that above provided information was resolved your query. Please let us know if you have any questions.
Håkon Lie 0 Reputation points

2025-10-27T07:14:29.28+00:00

Hi..
"We can confirm that the behavior you observed is expected."
"The AllowLowPriorityNode setting applies only to the JobManagerTask. This flag is intended to prevent preemption of long-running Job Manager tasks by low-priority nodes."

This is not the behiavor I observed. You must not have read my ticket at all? As this is in the title: "it seems to me that those other tasks inherit the "AllowLowPriorityNode: false" flag I have set on the job manager".

The behavior I observed is that other tasks added after the jobmanagertask does NOT run on lowpiority nodes when the flag is set to false on the jobmanager task

Answer 1

Hello Håkon Lie,

Thank you for describing your experience with Azure Batch jobs and the "AllowLowPriorityNode: false" setting on your JobManagerTask. Based on your observation, it does seem that tasks added to a job inherit constraints from the JobManagerTask, even though the field itself is only available there.

Here's what likely happens:

Inherited Constraints: If you set "AllowLowPriorityNode: false" on your JobManagerTask, all tasks within that job may be restricted from running on low-priority nodes by default, even if you do not set that option directly on the other tasks.

No Per-Task Override: The Azure Batch API currently exposes the "AllowLowPriorityNode" field only for the JobManagerTask, not for regular tasks. This means you cannot override the inherited restriction on a per-task basis from the portal or standard SDK.

Deployment Best Practices: If you need some tasks to use low-priority nodes and others to restrict them, consider splitting the work into separate jobs with tailored JobManagerTask settings.

Refer to the documentation on Jobs and tasks in Azure Batch and Job and Task Properties for more details.

Let me know if you need sample code or architectural guidance on separating jobs for granular control!

Best regards,

Jerald Felix

Jerald Felix MCT 7,990 Reputation points

2025-10-17T12:03:25.52+00:00

Håkon Lie , Just checking in did the answer help you fix the issue with adding more tasks to your job using the Job Manager task? 😊

If it worked, please mark it as Accepted so it can help others facing the same problem too.

If you’re still stuck or have any new errors, feel free to share more details. I’m here to help you get it sorted.

Best Regards,

Jerald Felix

Share via

When adding more tasks to a job with a JobManagerTask, it seems to me that those other tasks inherit the "AllowLowPriorityNode: false" flag I have set on the job manager

1 answer

Your answer