# Rosie go unresponsive / time mis-match

**URL:** https://cms-helpdesk.ncas.ac.uk/t/rosie-go-unresponsive-time-mis-match/1133
**Category:** Rose/Cylc and FCM
**Tags:** ARCHER2
**Created:** [15 September 2023 08:37 UTC](https://cms-helpdesk.ncas.ac.uk/t/rosie-go-unresponsive-time-mis-match/1133 "2023-09-15T08:37:58Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![bassett](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@bassett](https://cms-helpdesk.ncas.ac.uk/u/bassett)
#### Post date: [15 September 2023 08:37 UTC](https://cms-helpdesk.ncas.ac.uk/t/rosie-go-unresponsive-time-mis-match/1133/1 "2023-09-15T08:37:58Z")

</div>

Hi all,

Rosie go seems not to be syncing with archer2. The job I have running, see highlighted in screenshot, based on the log on archer2 succeeded 2 days ago (and the model output is there). The job history on Rosie go suggests it succeeded, then failed, but thinks it is still running

I’ve also notice a time mis-match - see bottom right of screenshot, this is about ~2days out.

I’ve tried a Nudge, Poll all and trying to mark the job manually as succeeded, no luck.

Any thoughts much appreciated.

Richard

 ![Screenshot 2023-09-15 at 09.20.28](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/e43898ac97dd9dd3128b8531e8e6bbb5c8d56cbb.png)

---

<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: [15 September 2023 08:52 UTC](https://cms-helpdesk.ncas.ac.uk/t/rosie-go-unresponsive-time-mis-match/1133/2 "2023-09-15T08:52:08Z")

</div>

Hi Richard,

I suspect it’s just that the cylc GUI has stopped communicating. If it’s not responding to polling, then you will need to shut it down and restart it. I suspect you won’t be able to shut the suite down via the GUI either but try that first. If it doesn’t respond then you will need to follow the instructions here: [Problems shutting down suites](https://ncas-cms.github.io/um-training/useful-information.html#problems-shutting-down-suites)

Cheers,  
Ros.

---

<div class="post-metadata">

### Author: ![bassett](https://avatars.discourse-cdn.com/v4/letter/b/ed655f/32.png) [@bassett](https://cms-helpdesk.ncas.ac.uk/u/bassett)
#### Post date: [15 September 2023 08:58 UTC](https://cms-helpdesk.ncas.ac.uk/t/rosie-go-unresponsive-time-mis-match/1133/3 "2023-09-15T08:58:37Z")

</div>

Thanks Ros.  
I’m assuming a ‘rose suite-run --restart’ in theory should just pick up where it left of after this?

Richard

---

<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: [15 September 2023 09:14 UTC](https://cms-helpdesk.ncas.ac.uk/t/rosie-go-unresponsive-time-mis-match/1133/4 "2023-09-15T09:14:36Z")

</div>

Yes. Or `rose suite-restart` if you don’t want it to reload any changes you may have made to the suite since you last started/restarted it.

Cheers,  
Ros.