I want to provide a quick update and also clarify my earlier post. After further review, the item I referenced (Epic ERPS-300291) has been rejected, and that’s the correct call. The decision to change this behavior was intentional.
Here’s why: the “MRP and Scheduling” logging option goes far beyond what’s practical for a normal daily MRP run. This level of detail creates a separate log file for every unfirm job and includes line-by-line scheduling activity. While that’s valuable for deep troubleshooting, it can generate thousands of files and consume excessive disk space — on both Cloud and On-Prem systems. It also slows MRP processing significantly.
The intent of this option has always been for on-demand use when you’re diagnosing a specific scheduling issue, not for routine or nightly MRP runs. For daily execution, the Basic or MRP logging levels provide all the necessary visibility without the performance or storage impact.
I apologize for my earlier message suggesting this was a bug being fixed. After revisiting the original design intent with the development team, it’s clear this was a purposeful change to align with how the feature was meant to be used.
Thanks to everyone who raised the question and shared feedback — it helped us make sure the reasoning is well understood and documented.