Able to schedule a node in past

Hi garg.karan, thanks for creating the MR. I need to replicate the problem first, then can review your solution. Is it possible that you could add test coverage for this, to demonstrate the problem and prove the fix. We have the 'test only changes' job in the pipeline which works very nicely to run updated tests on the original unchanged code.

Hi garg.karan, thanks for creating the MR. this works well with version:2.2.1.
Adding a patch file using your MR here for use.

I have tried, but not been able to replicate this problem, using Core 11.1 and Scheduler 2.2.1.

To be honest, I do not see any way that the label of the title field could affect the validation constraints anyway, but I am willing to try it, and be proved wrong. But until I can replicate the problem and ensure that it is a Scheduler bug it won't get much further. Maybe there is some unintended interaction with another module which is removing your validation constraints?

It's been two months since my request for information on how to replicate this, with no response.

@er.garg.karan @karavkars please give more details on how to reproduce this from a clean site install. Until we can do this, there won't be any more progress here. Thanks.