Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Chat triggers don't work with the new partial execution flow #11952
fix: Chat triggers don't work with the new partial execution flow #11952
Changes from 4 commits
60d81e2
df26d52
a78d8ce
4dbc563
b4dc389
02a4aa1
c50ffbe
924294b
b27590f
f68c0d7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The number of arguments to this function were getting out of hand so I turned it into an object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be an
else if
with the next check?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't follow.
This check is removing all but one webhook from the list if the preferred trigger was passed.
The next check is checking if the the list contains at least one trigger that is restartable (I think 🤔 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the question is, can it ever happen that a trigger to start triggers the restartable check? What exactly is
w.webhookDescription.restartWebhook
?But if not worth it let's leave it :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know either tbh. Jan added this here: 5a179cd#diff-b386248ff00977749c873ed85821c241b773e9740d7e7adf94e05b73b350ed74
Which is a huge commit.
It seems this is for the Form, Wait, Slack and Gmail nodes.
I guess that would be fine still. I'm assuming this is to not listen for webhook for workflows that have been put to into waiting?
Which means you can't actually pick them as a trigger to start from.
At least for the the wait and form nodes this is only interesting for workflows that wait, probably for slack too, e.g. if you render a dialog and wait for the user to click a button. I'm not sure why the gmail node offers this though.
I guess this can be left until the split button is implemented.
cc @cstuncsik @CharlieKolb