I have been following these instructions to run ACCESS-ROM3 from rest, with all the setup initiated from an interactive payu clone, etc. I’m using payu/1.3.5_0. Everything goes well until I run payu run, at which point I get the following error: [ERROR] 'str' object cannot be interpreted as an int…

after a back and forth with an AI coding agent, I was able to fix the problem. it seems like my personal cache was corrupted and putting strings in the PBS timestamp . e.g. "timestamp": "" instead of e.g. "timestamp":1788396111 I was able to fix by just moving out of the way my pbsnodes.json and…

Thanks for reporting @Wilton_Aguiar , and great you solved it youself. We have an existing issue for this, so it is clearly something that is affecting users and should be fixed.

Payu run str error with rom3

COSIMA Working Group

Qianhui_Chen (Qianhui Chen) 9 September 2026 06:35 4

Thank you @Wilton_Aguiar for reporting this!

This bug has now been fixed in payu/1.3.6 (see release post). Please don’t hesitate to reach out if you come across any other questions or issues.

Topic		Replies	Views
`payu run` issues COSIMA help , payu	2	66	17 July 2026
Payu: a workflow manager for some ACCESS models ACCESS-NRI Releases nci , release , payu , nri-updates	14	1276	9 September 2026
PAYU issues on Leonardo Technical help , payu	29	589	23 April 2025
PAYU issues on Setonix Technical payu	17	591	26 September 2023
Payu error Technical help	3	72	9 May 2025

Payu run str error with rom3

Related topics