Hello,
It seems that the issue occurs because of the duration_step parameter, so, the getClosestWorkTime method returns a wrong date.
I added it as a bug to our internal bug tracker. The dev team will fix the issue in the future, but I cannot give you any ETA.
As a workaround, you can specify the task duration without this parameter: https://snippet.dhtmlx.com/cexa4ahb
Get a guaranteed answer from DHTMLX technical support team
under the most suitable support plan