# SyteLine APS error 30012: what to check before rerunning > Source: https://netray.co/erp-help/syteline-aps-error-30012 > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer APS errors in SyteLine generally come from three places: the APS planning service itself, the data sync between SyteLine and the APS database, or bad source data such as a missing routing or calendar. I could not confirm an official definition for code 30012, so this page gives the diagnosis order that isolates the layer before you rerun the schedule. ## Kind error ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module APS / Planning and Scheduling ## Query syteline aps error 30012 ## Alternate Queries - SyteLine APS scheduling failed - APS planning service error SyteLine - SyteLine APS sync error ## Applies To SyteLine 9.x and CloudSuite Industrial 10.x with Infor APS (Advanced Planning and Scheduling) ## Steps ### Isolate the failing layer **Items:** - Record the full message, who ran APS, the planning site and the time. Note whether this was an interactive or scheduled run. - Confirm the APS services are running on the app or planning server and that the account they run under is valid and not expired. - Check that the SyteLine to APS sync tasks ran without error. Failed syncs leave APS with stale or partial data. - Review the sync and APS logs for the first error in the chain, not the last one. - Validate source data for the items in the failing run: item has a routing, work centers have a calendar and capacity, and no negative or zero lot sizes. - Check SQL Server for blocking or timeouts during the run, since APS reads and writes heavily. - Rerun on a small subset (one item family) to see if it is data-specific. - Only after the cause is fixed, run the full sync and schedule again, and compare the planned orders to expectations. ## Sections ### How APS fits with SyteLine **Body:** APS works on its own planning data set. SyteLine pushes demand, supply, items, routings and calendars into it through sync processes, APS computes the plan or schedule, and results flow back as planned orders and dates. An error can occur at the push, in the calculation, or in the return. That is why rerunning the schedule over and over rarely helps: if the sync failed upstream, APS is calculating from bad data and will fail the same way. ### Data problems that stop a schedule **Body:** The most frequent root causes are structural: an item with a routing referencing a deleted work center, a work center with no calendar, a calendar that ends before the horizon, circular or unusually deep BOM structures, and jobs with invalid dates. A clean-up pass on these often removes the error. Custom fields or modifications that write bad values into planning tables can also cause it. If the error started after a customization or upgrade, diff what changed. **Code:** -- Example read-only checks (adjust table names to your schema) -- Items with a routing referencing a work center that no longer exists -- Work centers without a calendar entry that covers the horizon -- Jobs with release date after due date ### Services, accounts and performance **Body:** If the services were restarted after a password change or server patch, they may be running under a stale account. Check the service logon, the database permissions, and whether antivirus or a firewall change blocks the planning server from reaching SQL. Long runs can also hit timeouts. See the APS performance tuning page for index and parameter guidance, and avoid running a full regeneration during peak transaction hours. ## Pitfalls - Rerunning the full schedule repeatedly without checking the sync. - Searching for the code alone and applying an unrelated fix. - Changing planning parameters while the underlying data problem remains. - Running APS during heavy order entry and blaming the software for blocking. - Not testing the fix on a small item subset first. ## Ai Angle SyteRay can read your SyteLine and planning tables to list the items, routings and work centers that violate the checks above, and show the query behind each finding. That turns an hour of manual SQL into a review list. It is read-only by default; any corrections go through your normal change process. ## Faq ### What does APS error 30012 mean in SyteLine? **Answer:** I could not find a reliable official definition. Treat it as an APS failure and isolate the layer: service, SyteLine to APS sync, or source data. The full message text and the first error in the logs are more informative than the number. ### Should I rerun the APS schedule right away? **Answer:** No. Fix the cause first. If the sync failed or the data is invalid, a rerun produces the same error or a misleading plan. Verify sync success and run a small subset first. ### Can bad routing data cause an APS failure? **Answer:** Yes. Missing work centers, work centers without calendars, or invalid operation data are common causes. Validate routings and calendars for the items involved before rerunning. ### How is this different from MRP regeneration failing? **Answer:** MRP failures originate in the standard planning process, while APS failures often involve the separate APS service and sync. The related MRP page covers the former. Some checks overlap, especially data quality and SQL contention. ## Search terms syteline aps error 30012, syteline aps error, infor aps scheduling error, syteline aps sync, csi advanced planning scheduling, syteline aps service, syteline schedule failed, syteline planning error --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json