Please open the support ticket, so we can identify the problem. The issue might be caused by incorrect job migration or by some "enviromental" specifics, which the new scheduler can't handle with. Opening the ticket, collecting the diagnostics and troubleshooting will help us a much.
Many thanks.
Honza