I may have bumped into a new bug: It seems none of...
# ask-communityo
Oscar Björhn
08/19/2022, 8:52 AMI may have bumped into a new bug: It seems none of my schedules are triggering anymore on 2.1.1, neither ones I've created with the --cron argument nor ones I've created manually in the GUI.
The flow runs show up as scheduled and then late. They are never processed by any agents (nothing shows up in their logs) and they do not show up under "upcoming runs" for the work queues.
I can run all of my deployments by triggering them manually, it's only the scheduled runes that don't get picked up.
Does anyone have working schedules in 2.1.1?
✅ 1
j
Jenny
08/19/2022, 9:18 AMHey @Oscar Björhn - thanks for flagging. I’m seeing if I can replicate this. Are you on Cloud or local Orion?
o
Oscar Björhn
08/19/2022, 9:55 AMI'm on cloud!
Oscar Björhn
08/19/2022, 9:56 AMAppreciate you checking it out, let me know if you need anything else from me.
Oscar Björhn
08/19/2022, 9:57 AMSome more info: Docker images, agents etc are all running 2.1.1. Deployments and queues are using the new name-based matchning method released in 2.1.0, not tags.
a
Anna Geller
08/19/2022, 11:00 AM
Hi @Oscar Björhn, we were able to replicate the issue you're seeing, thanks so much for reporting it! The same works on the OSS version, which may suggest some lag in the Cloud version. We are actively investigating and will update you here soon.
o
Oscar Björhn
08/19/2022, 11:57 AMNeat, thanks! 👍
a
Anna Geller
08/19/2022, 12:17 PM
we found out the issue, working on pushing a fix
🚀 1
Anna Geller
08/19/2022, 2:05 PM
@Oscar Björhn this has been released and fixed now, thanks again!
o
Oscar Björhn
08/19/2022, 2:09 PMNice, thanks for fixing it! 🙂
🙌 3
🙏 2
k
Khuyen Tran
08/19/2022, 2:44 PMThanks for the feedback @Oscar Björhn
4 Views