# Acumatica Automation Schedule Not Running: Causes and Fixes > Source: https://netray.co/erp-help/acumatica-automation-schedule-not-running-fix > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer If an Acumatica automation schedule does not fire, check that it is Active, that Next Execution is in the future and in the right time zone, that the schedule's user is valid, and review Schedule History for the failure. On premises, an idle IIS application pool is the classic hidden cause: the site must be warmed up and set to always run so the scheduler can trigger. ## Kind how-to ## System small-erp ## Erp Acumatica Cloud ERP ## Module System / Automation Schedules (SM205020) ## Query Acumatica automation schedule not running ## Alternate Queries - Acumatica scheduled process not executing - Acumatica automation schedule history - Acumatica schedule runs only when user logged in - Acumatica recurring report schedule not sending ## Applies To Acumatica Cloud ERP, Automation Schedules (SM205020), on-premises IIS deployments and SaaS tenants ## Steps ### How to troubleshoot a schedule that does not run **Items:** - Open System > Process Automation > Automation Schedules (SM205020) and select the schedule. Confirm Active is checked and the date range includes today. - Check Next Execution and the time zone. A schedule set for a time that already passed with no run suggests the scheduler was not alive. - Click Run Now. If it works manually, the business logic is fine and the issue is the scheduler or timing; if it fails, read the error. - Open Schedule History for the run and read the error or warning text. Failed items often include a validation issue on one record that stops the batch. - Verify the schedule's Run As user is active, not locked, and has access to the screen and the data (branch, company). - Confirm the screen's action works for a user with the same role; a missing role can silently block the action. - On premises, set the IIS application pool Idle Time-out to 0 and Start Mode to AlwaysRunning, and enable Preload on the site so the scheduler survives idle periods and restarts. - After changes, confirm the next run in Schedule History and set up email notification on failures for critical schedules. ## Sections ### How the scheduler works **Body:** Automation schedules are evaluated by the application itself, not by an external service. A timer inside the website process checks for due schedules and queues the work. If the process is stopped or recycled and nobody opens the site, nothing triggers on a plain IIS setup. On SaaS the platform keeps instances alive. On premises you own that responsibility, so IIS settings matter as much as the schedule definition. **Code:** IIS Manager > Application Pools > > Advanced Settings Start Mode: AlwaysRunning Idle Time-out (minutes): 0 Sites > > Advanced Settings Preload Enabled: True ### Data and permission causes **Body:** A schedule is a saved filter plus an action. If the filter returns no records, the run succeeds with nothing to do, which looks like it did not run. Check the filter conditions and the date logic, especially relative dates. If one record in the batch throws an error, such as a missing required field or a closed financial period, the history shows an error on that record while others may still process. Fix the data or exclude the record in the filter. ### Scheduled reports and emails **Body:** Scheduled reports and emails depend on a working email account in Email Preferences and the Email Templates. If the report runs but nothing arrives, check the outgoing mail account, the Mail log, and spam filtering on the receiving side. For heavy schedules, such as nightly releases, stagger start times so they do not all compete at midnight, and monitor with the License Monitoring Console for load. ## Pitfalls - Assuming the schedule is broken when IIS recycled the application pool overnight. - Running the schedule as a personal user whose password expired or whose account was disabled. - A filter that silently returns zero records after a data change. - Stacking many heavy schedules at the same minute. - Not monitoring failures and finding out weeks later. ## Ai Angle An AI assistant over Acumatica can read Schedule History across all schedules, summarize which failed, group the errors by cause, and tell you which record blocked a batch. ERPray reads this data without changing any schedule; changing the user, filter or IIS settings stays with your administrator. ## Faq ### Why does my schedule only run when someone logs in? **Answer:** On premises the IIS application pool probably goes idle and shuts down. Set Idle Time-out to 0, Start Mode to AlwaysRunning and enable Preload, so the scheduler stays alive without any user opening the site. ### Where can I see why a schedule failed? **Answer:** In Automation Schedules (SM205020), open the schedule and use the Schedule History tab or the View History action. Each run lists the processed records with status and the error message for any failed item. ### What user should a schedule run as? **Answer:** Use a dedicated service account with only the roles required, a password that does not expire, and access to the right branches. Avoid personal accounts that get disabled when employees leave. ### Can I trigger a schedule manually to test? **Answer:** Yes, use Run Now on the Automation Schedules screen. It runs the action with the saved filter immediately, which separates a logic problem from a scheduler or timing problem. ## Search terms acumatica automation schedule not running, acumatica SM205020, acumatica schedule history, acumatica scheduled process, acumatica iis idle timeout, acumatica scheduled report email, acumatica run now schedule, acumatica background process not running --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json