Skipping cycles without reinstalling

I am using cylc 8.2.3
I have a simple workflow, but it has quite a few tasks in it. I was doing some work on it and got side tracked with other tasks.

Now my initial cycle point is back in March with the last cycle running and finishing on March 28th, and now here I am in April. I know obvious answer is probably reinstall a new run with a new cycle point, but I am curious if there is a way to restart my March run and also progress the workflow to my current cycle without having to run all the missed cycles inbetween?

Anyone know of an existing function (cylc play my_workflow --restart-point=today) or got a cool trick for that (maybe a method to en masse succeed and remove all the missed cycles)?

Hi @Jaclyn

That is pretty easy to do, but exactly how to do it depends somewhat on the structure of your workflow, and how recent your Cylc version is - you should upgrade as 8.2.3 is pretty old, and we’re rapidly adding new features to make manual interventions easier.

Is that because you set a final cycle point as March 28, or just because the workflow was paused, shut down, or killed then? If it’s a final cycle point, you’ll obviously have to change that before continuing.

Generally speaking, to “fast forward” to a new cycle in Cylc 8 you can simply trigger the initial tasks of that cycle, and activity will flow on from those tasks as the graph dictates. A possible complication is that depending on your workflow graph the “initial tasks” of the cycle might be many and/or or tricky to identify, and there may be off-flow prerequisites that have to be manually satisfied with cylc set downstream of the initial tasks to prevent the new flow from stalling.

Another way to do this, since 8.4.0, is the “skip” run mode, which lets you skip ahead in the graph by essentially telling Cylc to simulate the execution of the intervening graph section. From the cylc-flow change log:

Added a new task run mode “skip” in which tasks instantly generate their required outputs without actually running. This allows us to configure tasks to “skip” ahead of time, e.g. to skip a cycle of tasks that is no longer needed.

Coming up in 8.5 we have a new “group trigger” feature that allows you to trigger the flow (e.g. in the future graph, like you want) without having to manually handle off-group prerequisites. However, that’s not released yet.

If you want to post your workflow graph, or perhaps a cut-down version of it with similar structure, then I can probably describe exactly how to do it.

See this entry in the intervention guide which shows how to skip a cycle of tasks using “skip mode”:

You will need to upgrade from Cylc 8.2 to use this. Running workflows can be restarted with newer versions of Cylc to upgrade them, they will continue running as expected when restarted.