Share via

Pool Nodes in "Unusable" state and then leaving the pool

Angelina Souy 40 Reputation points
2025-09-10T13:41:18.1133333+00:00

Since 2 hours ago, pool nodes that are automatically created become "Unusable" and then leave the pool, despite no recent changes made.

All tasks are stuck in the active state because of this looping issue.

No errors are visible that would clarify the source of the issue.

What steps could be taken to resolve this issue?

I would appreciate a quick support as it's preventing us from running important automated tasks.

Azure Batch
Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
Answer accepted by question author
  1. Ankit Yadav 4,145 Reputation points Microsoft External Staff Moderator
    2025-09-10T21:56:20.5666667+00:00

    The issue was caused by a corrupted application file, which prevented the pool nodes from initializing properly.

    As a result, the nodes were marked as Unusable and automatically exited the pool, leaving no active nodes to process tasks. This caused all tasks to remain in the active state. Once the corrupted file was identified and addressed, the nodes were able to start successfully, resolving the issue

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.