# D365 Finance and Supply Chain Batch Job Checklist > Source: https://netray.co/tools/d365-batch-job-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A practical checklist to design, review and monitor batch jobs in D365 F&O, covering batch groups, recurrence, alerts, cleanup jobs and go-live checks. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - D365 F&O administrator - D365 F&O consultant - IT operations ## Tool **Kind:** checklist **Groups:** #### Design and inventory **Items:** **Text:** List every recurring batch job by business owner, purpose and expected runtime **Critical:** true Document which jobs are system-required, such as master planning, and which are optional Record each job's dependencies on other jobs or on external files **Text:** Confirm each job runs under a dedicated service or integration user, not a personal account **Critical:** true Check the user has the roles needed for the job and the legal entities it runs in Capture the legal entity each batch job runs in #### Batch groups and servers **Items:** Define batch groups by workload, such as planning, integration and posting **Text:** Assign AOS instances to batch groups in System administration > Setup > Batch groups **Critical:** true Set the maximum batch threads per instance and review them after load tests Keep long-running planning and posting jobs from starving short integration jobs Check whether the environment has dedicated batch capacity, especially in production Review the 'Excluded from batch' behavior of AOS instances where relevant #### Scheduling and recurrence **Items:** **Text:** Set recurrence with an explicit start time and time zone for each job **Critical:** true Stagger heavy jobs so they do not all start at the top of the hour Define an end date for temporary jobs created for migration or testing Avoid overlapping runs of the same job and set a sensible 'maximum number of retries' Use batch job dependencies or sequential tasks for chained processes **Text:** Keep a calendar of jobs to pause during a deployment or update window **Critical:** true #### Monitoring and alerts **Items:** **Text:** Review System administration > Inquiries > Batch jobs for Error and Withhold statuses daily **Critical:** true **Text:** Configure batch job alerts for the Error status to a monitored mailbox or channel **Critical:** true Review batch job history and the log of each failed run, not just the status Track runtime trends per job to spot growth before it breaks the window Set up telemetry or monitoring that surfaces long-running or stuck jobs Define who owns each failed job and the response time expected #### Housekeeping jobs **Items:** **Text:** Schedule batch job history cleanup so history tables do not grow without limit **Critical:** true Schedule cleanup for other history tables relevant to your modules, such as update histories Review inventory-related cleanup and settlement jobs as recommended for your version Confirm integration logs and staging tables are cleaned on a defined retention Verify cleanup jobs do not run in the middle of the busiest business hours #### Go-live and change control **Items:** **Text:** Recreate or re-enable batch jobs after a database refresh, since jobs can be withheld **Critical:** true Check that integration jobs point to the right endpoints in each environment Include batch job review in the release checklist for every update Test failure handling by forcing an error in a sandbox and confirming alerting works Record every batch job change in your change log with the approver **Scoring Note:** Every critical item should be complete before go-live. Anything unchecked is a risk to log with an owner and a date. ## Content **Intro:** Batch jobs run master planning, posting, integrations and cleanup in Dynamics 365 Finance and Supply Chain. When they fail quietly, planners work from stale data and integrations lag. Use this checklist to design, review and monitor them. **Sections:** #### How to use the checklist **Body:** Work through each group with the administrator and a functional owner. Mark items complete as you verify them in the environment, and note exceptions. Print it or export to PDF for the go-live record. Revisit it after each update cycle and after any database refresh to a sandbox, because job statuses and users can change. **Bullets:** - Start with the inventory of jobs and owners - Review batch groups and thread settings together - Confirm alerting works before relying on it - Repeat the review each release cycle #### How batch processing works **Body:** A batch job holds one or more tasks that run on AOS instances assigned to batch groups. Jobs have a status such as Waiting, Executing, Ended, Error or Withhold, and can recur on a schedule. Concurrency is bounded by the batch threads per instance, so many heavy jobs in one group queue behind each other. Understanding this explains most performance complaints about overnight windows. #### Monitoring habits that work **Body:** The most effective habit is a daily check of the batch jobs list filtered to Error and Withhold, plus alerts so nobody depends on that check alone. For each failure record the root cause, not only the retry. Common causes are missing permissions on the executing user, locked or invalid data, an external endpoint that was down and jobs that collide on the same records. #### Common mistakes **Body:** Teams often run everything in the default batch group, leave jobs under a personal user who later leaves, forget that refreshing a sandbox from production may withhold jobs, and never schedule history cleanup. Another is creating test jobs with no end date that keep running for years. **Cta:** If you want failed-job summaries and runtime trends answered in plain language from your D365 data, we can discuss a read-only assistant for your administrators. **Faq:** #### Where do I see batch jobs in D365 F&O? **Answer:** Go to System administration > Inquiries > Batch jobs. You can filter by status, view job history, open the log of a run and change recurrence. Batch groups are set up under System administration > Setup > Batch groups. #### Why are my batch jobs in Withhold status? **Answer:** Withhold means the job will not run until it is set to Waiting. It often happens after a database refresh to a sandbox, where jobs are withheld on purpose to avoid duplicate external effects. Review each job before enabling it. #### How many batch threads should I set? **Answer:** There is no universal number. It depends on the instance size and workloads. Start with the platform default, load test peak windows, and watch for contention on shared data before raising it. Separate batch groups often help more than raw thread counts. #### Which cleanup jobs should I schedule? **Answer:** At minimum schedule batch job history cleanup, then add module-specific cleanup routines recommended in documentation for your version, such as various update history and log cleanups. Run them off-peak and review their impact in a sandbox first. ## Search terms d365 batch job checklist, d365 batch job best practices, dynamics 365 batch jobs monitoring, d365 batch group setup, d365 recurring batch job, d365 cleanup batch jobs, d365 batch job error troubleshooting, d365 f&o system administration batch --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json