Error on pressing “Done” at Setup (CONN version 19.c)

I am analysis on data obtained during a motor task from 9 participants. The data had been analysed before (not with CONN) so I already have SPM.mat files for each participant and I just imported them by selecting the \"Convert/Import from SPM design files\" option in the \"Tools\" menu, specifying 9 participant placeholders, and then associating with them the respective SPM.mat files.

However, when I click "Done" in the setup tab, I get the following error for participant 1:
SOME ERRORS FOUND!: Please revise the Setup information
ERROR: Subject 1 Session 2 condition 2_3_Session2 contains onset times beyond the end of the scanning session
ERROR: Subject 1 Session 2 condition 2_10_Session2 contains onset times beyond the end of the scanning session
E:\\projects\\tsvet\\connfMRI\\conn_project05.qlog\\201026003449602\\node.0001201026003449602.bat error
ERROR DESCRIPTION:
Error using conn_process (line 225)
ERROR: Subject 1 Session 2 condition 2_3_Session2 contains onset times beyond the end of the scanning session
ERROR: Subject 1 Session 2 condition 2_10_Session2 contains onset times beyond the end of the scanning session
Error in conn_process (line 16)
case \'setup\', conn_disp([\'CONN: RUNNING SETUP STEP\']); conn_process([0:4,4.5,5]);
Error in conn_jobmanager (line 798)
conn_process(job(n).fcn,job(n).args{2:end});

I looked in the "Conditions" tab. Indeed, for these conditions in run 2 the onset times of these two specific trials trials were respectively 461.17 secs with duration of 0 secs, and 459.76 secs with a duration of 1.014 secs, which is not possible as run two was only 454 secs (227 volumes with TR of 2).

I have come across with a thread of some people having similar issues (https://www.nitrc.org/forum/forum.php?thread_id=9670&forum_id=1144). There a patch was provided but for an older version. Is there a solution for this version?
Also, I am conducting the denoising in parallel for all 9 participants, if this is important.

I have tried completing pre-processing through versions 16.b and 18.b but the same mistake occured.

Thanks,
Ivan