# Fixing "There are currently no batch servers available for processing" in D365 F&SCM > Source: https://netray.co/erp-help/dynamics-365-fo-batch-job-no-batch-servers-available > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer This message means the batch framework cannot find any AOS instance flagged as a batch server and available for the batch group the job is assigned to. The fix is almost always in server configuration (System administration > Servers) or batch group assignment, not in the batch job itself. ## Kind error ## System dynamics ## Erp Microsoft Dynamics 365 Finance and Operations (F&SCM) ## Module System administration / Batch framework ## Query There are currently no batch servers available for processing D365 finance and operations ## Alternate Queries - D365 batch job stuck waiting forever - no batch servers available for processing error - D365 finance and operations batch job not running ## Applies To Dynamics 365 Finance and Operations (Finance, Supply Chain Management), cloud and on-premises; the same server/batch-group model existed in AX 2012. ## Steps ### Diagnose a stuck or failing batch job **Items:** Go to System administration > Periodic tasks > Batch jobs and check whether the affected job is stuck in Waiting rather than Executing. Go to System administration > Servers and confirm at least one active AOS instance has Is batch server (or the equivalent server-role flag) enabled. Open System administration > Setup > Batch group and confirm the batch group the job runs under has at least one server assigned to it. Check whether the server assigned to that batch group is actually online: an entry that exists but whose underlying service is stopped will still fail to pick up work. Look at Batch job history for the specific job to see the last status change and any error message logged against individual batch tasks, not just the parent job. In cloud-hosted environments, check environment health/monitoring for the AOS role rather than assuming a service restart is needed, since scale-out or maintenance windows can temporarily remove batch capacity. Once a server is confirmed enabled and online for the correct batch group, resubmit or requeue the stuck batch task rather than only creating a new one, so history stays consistent. For recurring integration or heavy batch load, review Maximum batch threads and how many long-running tasks are consuming threads, since threads exhausted by one job can make new jobs appear as if no server is available. ## Sections ### How the batch framework decides where to run **Body:** Every batch task is submitted against a batch group, and every batch group has one or more AOS instances assigned to it that are also flagged as batch servers. When the batch scheduler looks for a server to pick up a waiting task, it only considers servers that satisfy both conditions: assigned to that batch group and currently online as a batch server. If either condition is not met - no server is flagged for batch processing at all, or the servers that are flagged are not members of the batch group the job was submitted under - the scheduler has nothing eligible to hand the task to, and it reports there are no batch servers available. ### Common root causes **Body:** The most frequent cause after an environment refresh or new deployment is that no AOS instance has been re-flagged as a batch server, because that configuration is environment-specific and is not always carried over automatically. A second common cause is a batch group created for a specific integration or module that was never assigned any server, so any job submitted under that group sits in Waiting indefinitely even though other batch groups are processing normally. A third cause is thread exhaustion: a small number of long-running or misbehaving batch tasks can consume all available batch threads on the only enabled server, so new tasks technically have a server assigned but nothing is available to process them, which looks the same to an end user as no server being configured. ### Operational monitoring **Body:** Because this failure mode is invisible until someone notices a job never ran, it is worth periodically reviewing the batch job list filtered to Waiting status with an age threshold, rather than only reacting when a business process visibly breaks. In multi-AOS environments, distribute batch groups deliberately across servers so a single server outage does not stall every integration and periodic process at once. ## Pitfalls - Assuming the parent batch job's status reflects every task; individual tasks inside a job can fail or stall independently. - Enabling a server as a batch server but forgetting to add it to the batch group the failing jobs actually use. - Not distinguishing a server that is offline from one that is simply not assigned to the right batch group; both look like "no server available" to end users. - Letting one runaway recurring job consume all batch threads so unrelated jobs starve. - Re-creating a batch job instead of investigating why the original task never got picked up, which hides the recurring root cause. ## Ai Angle A grounded assistant with read access to batch job history, server configuration, and batch group assignment in a customer's environment can answer "why is this job stuck" directly - correlating the waiting task to its batch group, checking whether any online server belongs to that group, and flagging thread exhaustion from other jobs - instead of an administrator manually opening three separate configuration forms to piece the picture together. ## Faq ### What is the difference between a batch server and a batch group? **Answer:** A batch server is an AOS instance that has been configured to accept and execute batch work. A batch group is a label a batch task is submitted under; the scheduler only routes a task to servers that are both online and assigned to that specific batch group. ### Why does one batch group work fine while another is stuck? **Answer:** Because server-to-group assignment is configured per group. A server can be flagged as a batch server and still not be a member of the group a specific stuck job uses, which leaves that group with zero eligible servers even while others process normally. ### Can a stuck batch task be forced to run on a different server? **Answer:** Yes, once you fix the underlying server or batch group configuration, resubmit or requeue the specific batch task rather than leaving the old waiting task in place, so the scheduler picks it up with a clean status. ### Is this the same issue that existed in AX 2012? **Answer:** The mechanism is the same batch framework concept carried forward from AX 2012 into Dynamics 365 Finance and Operations: server flags plus batch group membership determine eligibility, so the same diagnostic steps apply on both versions. ## Search terms no batch servers available for processing d365, d365 batch job stuck waiting, dynamics 365 finance operations batch server setup, d365 batch group configuration, d365fo batch job not running, system administration servers batch server flag, d365 batch job history troubleshooting, batch thread exhaustion d365, dynamics ax batch group vs batch server --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json