# ARCHER2 cylc version suddenly reverted?

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185>\
**Category:** Rose/Cylc and FCM\
**Tags:** ARCHER2, PUMA2\
**Created:** [28 September 2026 13:04 UTC](https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185 "2026-09-28T13:04:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![racheldiamond](https://avatars.discourse-cdn.com/v4/letter/r/eb9ed0/32.png) [@racheldiamond](https://cms-helpdesk.ncas.ac.uk/u/racheldiamond)\
**Post date:** [28 September 2026 13:04 UTC](https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185/1 "2026-09-28T13:04:34Z")

</div>

Hi,

I previously had an issue where tasks were failing to submit from puma2 to ARCHER2. Ros fixed this by noticing my ARCHER2 ~/.bash\_profile was pointing to a very old UM environment with cylc version 7: [https://cms-helpdesk.ncas.ac.uk/t/submit-failed-puma2-to-archer2/2121/3?u=racheldiamond](https://cms-helpdesk.ncas.ac.uk/t/submit-failed-puma2-to-archer2/2121/3)

My suite u-ea675 was running fine but this morning around 6am stopped with similar submit-failed errors. I checked on ARCHER2 and again have cylc --version 7.8.12 (instead of cylc 8). Nothing in my bash profile has changed.

How should I fix this? I’m a bit nervous to try lots of different restart methods as u-ea675 is meant to be bit-comparable to another running suite.

Best wishes,

Rachel

---

<div class="post-metadata">

**Author:** ![jonnyhtw](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/jonnyhtw/32/548_2.png) [@jonnyhtw](https://cms-helpdesk.ncas.ac.uk/u/jonnyhtw)\
**Post date:** [28 September 2026 13:43 UTC](https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185/2 "2026-09-28T13:43:11Z")

</div>

Hi Rachel.

Couple of questions…

1. What is your PUMA2/ARCHER2 username?
2. What do you get when you run `cylc --version` on PUMA2?
3. What do you get when you run `which cylc` on PUMA2

This is what I get…

```auto
$ cylc --version

8.6.3

$ which cylc

/home/n02/n02/fcm/metomi/bin/cylc

```

It’s possible too that even though you’ve made sure you’re using Cylc 8 on PUMA2 that it is being set to use version 7 on ARCHER2. I have `export CYLC_VERSION=8` in my startup scripts on PUMA2 and ARCHER2.

Also, if you’re restarting from a previously stopped job which ran with Cylc 7 then it will automatically pick version 7 again even if you have version 8 hardcoded in your startup scripts. Restarting using a different Cylc version is possible but is fraught with potential potholes.

Cheers

Jonny

---

<div class="post-metadata">

**Author:** ![racheldiamond](https://avatars.discourse-cdn.com/v4/letter/r/eb9ed0/32.png) [@racheldiamond](https://cms-helpdesk.ncas.ac.uk/u/racheldiamond)\
**Post date:** [28 September 2026 15:22 UTC](https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185/3 "2026-09-28T15:22:04Z")

</div>

Hi,

My PUMA2 and ARCHER2 username is radiam24 (met office username is racheldiamond). On PUMA2 I get cylc version 8.6.3, and which cylc \>  
/home/n02/n02/fcm/metomi/bin/cylc.

I’m trying to restart a job that was running fine yesterday and I haven’t changed anything since then, just started suddenly getting submit-failed messages this morning. So it’s possible it’s not related to the CYLC version at all, I just assumed it was because of Ros’s fix on the previous problem in July.

Thanks!

Rachel

---

<div class="post-metadata">

**Author:** ![jonnyhtw](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/jonnyhtw/32/548_2.png) [@jonnyhtw](https://cms-helpdesk.ncas.ac.uk/u/jonnyhtw)\
**Post date:** [28 September 2026 16:10 UTC](https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185/4 "2026-09-28T16:10:19Z")

</div>

Thanks for that info Rachel. It’s possible that the project you’re submitting under has reached budget. We’ll get back to you on this.

```auto
$ cat /home/n02/n02/radiam24/roses/u-ea675/rose-suite.conf|grep -i archer2_group

ARCHER2_GROUP='n02-SURFEIT'

```

Cheers

Jonny

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [28 September 2026 18:48 UTC](https://cms-helpdesk.ncas.ac.uk/t/archer2-cylc-version-suddenly-reverted/2185/5 "2026-09-28T18:48:59Z")

</div>

Hi Rachel,

n02-SURFEIT has indeed used up all of its allocation.

FYI you can see the error message in e.g. `~/cylc-run/u-ea675/run2/log/job/31051101T0000Z/postproc_archive/10/job-activity.log`

```auto
2026-09-28T15:40:30Z \[STDERR\] sbatch: error: AssocMaxCpuMinutesPerJobLimit
2026-09-28T15:40:30Z \[STDERR\] sbatch: error: Batch job submission failed: Job violates accounting/QOS policy (job submit limit, user's size and/or time limits)

```

And if you look in SAFE you can see what allocation you have remaining.

How many more CUs do you need to complete your run?

Regards,  
Ros