-
Hi 👋t2:. I’ve been playing around with the workflow_run event, and came across somewhat of an issue/unexpected behaviour. Given a workflow like this:
Expected: Assuming a workflow run named “do something” has being requested, there will be two additional workflow runs triggered, one for the “requested” phase, and another one for the “completed” phase. Unexpected: So, to summarise, re-running a workflow, I would expect two additional workflow runs, and not just one. P.S eladchen/workflow-run-webhook-demoContribute to eladchen/workflow-run-webhook-demo development by creating an account on GitHub. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Thanks for your feedback. I can reproduce the same behavior as you reported. If you really need the feature that workflow_run event can support the activity type ‘re-run’, I recommend that you can directly report a feature request here. |
Beta Was this translation helpful? Give feedback.
-
Thank you, I’ll do that. |
Beta Was this translation helpful? Give feedback.
-
It just stroke me that this is not a feature request, but more of a bug (“workflow._run.completed” does trigger when “re-run”) How can I report this as a bug…? |
Beta Was this translation helpful? Give feedback.
@eladchen ,
Thanks for your feedback.
I can reproduce the same behavior as you reported.
Looks like, ‘re-run’ is not considered as an ‘requested’. Only triggering a workflow run at the first time can be considered as ‘requested’.
If you really need the feature that workflow_run event can support the activity type ‘re-run’, I recommend that you can directly report a feature request here.
That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions.