Opened 8 days ago

Last modified 8 days ago

#2760 new help

Jobs stuck at previous cycle but has carried on somehow (u-be496, u-be497, u-bf405)

Reported by: cwc46 Owned by: um_support
Priority: normal Component: UM Model
Keywords: Cc:
Platform: ARCHER UM Version: 11.0


Dear NCAS helpdesk,

Somehow my jobs have been stuck at a previous cycle but has also succeeded running subsequent cycles, and I was wondering if there was something wrong..

I have attached a screenshot of one of my jobs, u-be496. My cycling frequency is 1 month but it seems to have succeeded running two months after the month it is currently stuck at.

Thank you!
Best wishes,

Attachments (1)

u-be496.png (34.1 KB) - added by cwc46 8 days ago.

Download all attachments as: .zip

Change History (3)

Changed 8 days ago by cwc46

comment:1 Changed 8 days ago by grenville


Rose Bush indicates that cycle 20020101T0000Z succeeded several days ago. I don't know why it is retrying. You should be able to see data for 20020101T0000Z. Check if its data is on the RDF. If it is, (along with other data you expect to see), you could set the task status to true.

We generally ask that users allow us read access to /nerc to assist with queries.


comment:2 Changed 8 days ago by cwc46

Dear Grenville,

Thanks for your reply - actually somehow I reset the task status to ready and it's now proceeded on as per normal. No idea what happened!

And regarding read access to /nerc, yes I will keep that in mind next time; I had only followed the instructions given on the CMS helpdesk homepage and given read access to my /home and /work.

Thank you very much!

Best wishes,

Note: See TracTickets for help on using tickets.