# Cylc8 -- continue not working **URL:** \ **Category:** Uncategorized\ **Created:** [31 July 2025 12:14 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761 "2025-07-31T12:14:05Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SimonTett](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SimonTett](https://cms-helpdesk.ncas.ac.uk/u/SimonTett)\ **Post date:** [31 July 2025 12:14 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761/1 "2025-07-31T12:14:05Z")
Dear helpdesk, I have modified suite u-dr157 by increasing the total run length from P3M to P36Y. To make it continue, I have done: > export CYLC\_VERSION=8 > > cylc play u-dr157 > > cylc trigger u-dr157 //19790401T0000Z/atmos\_main but I get an error message: WorkflowStopped: u-dr157/run6 is not running If I go to the gui interface and click the play button, I get a different error message Command failed: play - It is not advisible to restart a workflow with an older version of Cylc than it was previously run with. - > 1. This workflow was previously run with 8.4.4. > 2. This version of Cylc is 8.4.2. > Use --downgrade to disable this check (NOT RECOMMENDED!) or use a more recent version e.g: > $ CYLC\_VERSION=8.4.4 play --color=never --mode live u-dr157/run6 How do I make it run….. ta Simon ---
**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\ **Post date:** [31 July 2025 13:04 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761/2 "2025-07-31T13:04:33Z")
Simon The quickest way will be to start a new run. It’s not clear what has happened in this case. Grenville ---
**Author:** ![mdalvi](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@mdalvi](https://cms-helpdesk.ncas.ac.uk/u/mdalvi)\ **Post date:** [31 July 2025 13:11 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761/3 "2025-07-31T13:11:25Z")
Note also that the [scheduling] section needs the keyword _stop after cycle point_ instead of _final cycle point_ to restart a workflow that has completed its (original) tasks. > **[Extending Workflow — Cylc 8.5.0 documentation](https://cylc.github.io/cylc-doc/latest/html/user-guide/examples/extending-workflow/index.html#extending-workflow)** This is a Cylc-8 change, while Cylc-7 suites could be restarted by redefining the final cycle point. Edit: I see that u-dr157 already [uses](https://code.metoffice.gov.uk/trac/roses-u/browser/d/r/1/5/7/trunk/flow.cylc?rev=327355#L75) the recommended keyword. ---
**Author:** ![SimonTett](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SimonTett](https://cms-helpdesk.ncas.ac.uk/u/SimonTett)\ **Post date:** [31 July 2025 13:56 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761/4 "2025-07-31T13:56:34Z")
I did that. Now it is taking its usual ages to run fcm\_make2\_um… I vaguely understand why cylc generates a new run every time. I just wish it would use make and grab the old fortran/.o files. That would make a huge difference to development speed…. Simon ---
**Author:** ![SimonTett](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@SimonTett](https://cms-helpdesk.ncas.ac.uk/u/SimonTett)\ **Post date:** [31 July 2025 14:38 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761/5 "2025-07-31T14:38:34Z")
and I think the answer to my problem is to do: cylc vip --no-run-name suite\_name Though, I have no idea if rerunning will avoid building the whole model anew. Simon ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/1fd2411499ffcbc299fe756cd5cdf26e44956558.png) [@system](https://cms-helpdesk.ncas.ac.uk/u/system)\ **Post date:** [30 August 2025 14:39 UTC](https://cms-helpdesk.ncas.ac.uk/t/cylc8-continue-not-working/1761/6 "2025-08-30T14:39:21Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.