Routine JULES workflow failing to run on JASMIN

JULES
1

Hi,

I have a routine JULES workflow that updates the operational TAMSAT all-Africa soil moisture dataset. The suite, running on Cylc2 on JASMIN, is configured to execute automatically when new driving data become available. Normally, when new data are detected, the workflow runs for the next cycle point, triggering the sequence of jobs as expected. However, in the current case, the workflow fails to start even though new data are available. The scheduler log file (/home/users/rmaidment/cylc-run/u-do123/log/scheduler) reports that this workflow already ran to completion. In this instance, the previous cycle (49) completed successfully, and the issue arises with the next cycle (50), which does not start as intended. I’ve edited the suite.rc file so that initial cycle point = 50 to be certain it’s starting at the correct cycle point, yet this doesn’t help.

The suite is u-do123 and is running from /home/users/rmaidment/cylc-run/u-do123.

Does anyone have any ideas as to what might be causing the issue?

Many thanks,
Ross

2

Hi Ross,

I’m not sure exactly why the suite has decided it’s finished as I can’t see a final cycle point set, but this isn’t a suite that I’m familiar with. However, I think if you restart the suite and then manually trigger the first task in the next cycle that should get it to continue. You will need to issue the trigger command within 5 minutes of restarting the suite, as per the warning at the end of the scheduler log file.

The trigger command is: cylc trigger <workflow-name> //50/<name-of-first-task>

Cheers,
Ros.

3

Hi Ros,

Thanks for the prompt reply - your suggestion worked perfectly!

Thanks very much,
Ross