Caelan U.

@Marvin9 yes, please feel free to open a PR if you have time this week since this is a higher priority bug and went stale. We will ensure you have...

Update: we are working on a larger code refactor (#10191) that will resolve this issue, but it was delayed by the holiday season. We will update again asap.

@alexec would you be able to lend us your thoughts on the below questions @goock proposed [above](https://github.com/argoproj/argo-workflows/issues/9193#issuecomment-1241901976)? > I see four possible solutions to the issue, but I need advice...

Thanks for the input @alexec ! @goock - do you still have capacity to work on this issue? We're trying to get a sense so we can prioritize it among...

Thanks for the quick update @goock ! That sounds like a plan. Feel free to post if further questions/ clarification needed.

Thanks for documenting this issue! We'll keep tabs on it and dig in if we get more bug reports related to it. We are currently working on other high-priority bugs.

Thanks, all! Happy to help out and lend a hand on the sig going forward 🙌

Thanks a lot for posting this issue w/ logs, a repro workflow, and even proposing a workaround for the time being. ❤️ We're doing some digging of our own into...

Also, FYI for SIGTERM related issues: https://github.com/argoproj/argo-workflows/issues/10518 PR: https://github.com/argoproj/argo-workflows/pull/10523

If you weren't having this issue until 3.4.5, then that will likely fix it. If you're able to test that PR or master with your repro workflow, please let us...