You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We are using Argo Events to trigger our Argo Workflows. Recently we noticed that when you update an existing workflow while it's running, it starts new workflows without getting an event.
To Reproduce
Steps to reproduce the behavior:
Create a workflow with a trigger
Trigger it.
Update workflow while it's running.
Check Argo Workflows UI and you'll see it runs a few more(it depends).
You might need to do this a few times to see it.
Expected behavior
When you update a workflow while it's running shouldn't spawn new runs.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Kubernetes: v1.27.4+k3s1
Argo: v3.4.11
Argo Events: v1.7.6
Additional context
I tried to reproduce this using only Argo Workflows but couldn't reproduce it. So I thought it's probably related to Argo Events. That's why I opened the issue here. Please let me know if I should do otherwise.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Describe the bug
We are using Argo Events to trigger our Argo Workflows. Recently we noticed that when you update an existing workflow while it's running, it starts new workflows without getting an event.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When you update a workflow while it's running shouldn't spawn new runs.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
I tried to reproduce this using only Argo Workflows but couldn't reproduce it. So I thought it's probably related to Argo Events. That's why I opened the issue here. Please let me know if I should do otherwise.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: