Hi,
One of our automation schedules failed before the scheduled screen could initialize. The only exception available in System Monitor is:
PX.Data.PXInvalidOperationException:
The initialization of the form failed due to an unexpected error.
The execution of the schedule was canceled.
at PX.Data.Process.ScheduleProcessor.SetCurrentScheduleAndCollectScrenInfo(...)
at PX.Data.Process.ScheduleProcessor.ProcessSchedule(...)
at PX.Data.Process.ScheduleProcessor.TryProcessSchedule(...)There is no inner exception showing the actual cause. Acumatica continued retrying the overdue schedule. Later, the website restarted automatically, and the schedule ran successfully after the restart without any configuration changes.
Has anyone encountered this behavior?
Specifically:
- Where can we find the underlying exception when System Monitor only shows this wrapper?
- Are additional server-side scheduler or application logs available?
- Could stale screen/customization cache cause initialization to fail until the website restarts?
- Is there a recommended way to add diagnostic logging for failures occurring inside
SetCurrentScheduleAndCollectScrenInfo?
This is a production environment, so we want to identify the cause and prevent another silent initialization failure.
Version 2026R1
Thank you.