Hi All, I’m not sure if this is a bug. When I use the browser UI or Classic UI or Kinetic UI and set MRP to run on a schedule and select Logging Level MRP and Scheduling I receive an error: Business Layer Exception Logging Level should be Basic or MRP when process is not scheduled for Immediate …

I can confirm this in 24.2.21 with new schedules. This is really bad.

They are going to say submit an Idea to change this…

Epicor support appear to acknowledge this as a ‘bug’ / problem and have raised a ticket to fix. I think this was causing Epicor problems for cloud customers and disk space. I’m on-prem so Epicor should not have this type of restriction.

Can you share the PRB? The restriction is equally unacceptable for cloud and on prem.

[image] rppmorris: I think this was causing Epicor problems for cloud customers and disk space. I believe that. [image] MLPegging log is hundreds of megabytes in size? That normal? Kinetic ERP Multi-level pegging, of course. We run it as part of MRP (not a separat…

[image] rppmorris: I think this was causing Epicor problems for cloud customers That doesn’t mean they need to put the shackles on everyone. Fix their shitty cloud hosting.

Well… [Sci-Fi GIF by Amazon Prime Video]

Thanks everyone for bringing attention to this and for the detailed examples. I wanted to share an update: this issue has been logged as Epic ERPS-300291, and Development officially accepted it yesterday. It’s now assigned to a developer and being actively worked. To clarify, this isn’t something s…

MRP on a schedule

Kinetic ERP

rppmorris (Roberto Morris) November 7, 2025, 12:43pm 22

PRB0307586
Development Task TASK7459797 added to support this case.

MLPegging log is hundreds of megabytes in size? That normal?