Hi,
We are noticing an error that happens (sometimes) when we are d&d in the scheduler. We cannot find an exact scenario to reproduce the issue, looks like some kind of race condition that only happens in a specific scenario. On some environments it always happens, on others sometimes.
The issue itself does not really have an impact i think but the biggest issue is that it is an uncaucht exception that breaks the scheduler -> the user has to refresh to be able to do any new action in the scheduler.
You can find the stack trace below. You can contact us to get an org where this issue is present.
Present in latest release 5.6.6
