-
Notifications
You must be signed in to change notification settings - Fork 13.4k
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(core): "Respond to Webhook" should work with workflows with waiting nodes #12806
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
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.
Michael confirmed testing so I only did code review.
@@ -94,13 +94,15 @@ export class ActiveExecutions { | |||
await this.executionRepository.updateExistingExecution(executionId, execution); | |||
} | |||
|
|||
const resumingExecution = this.activeExecutions[executionId]; |
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 we use ActiveExecutions.getExecution
every time we access one?
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.
getExecution
throws, and in this case we don't want that.
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.
It'd be nice to rename to getExecutionOrFail
|
n8n
|
Project |
n8n
|
Branch Review |
CAT-545-respond-with-wait
|
Run status |
|
Run duration | 04m 39s |
Commit |
|
Committer | कारतोफ्फेलस्क्रिप्ट™ |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
1
|
|
5
|
|
0
|
|
433
|
View all changes introduced in this branch ↗︎ |
|
1 similar comment
|
✅ All Cypress E2E specs passed |
Got released with |
Summary
When an execution goes into the waiting state, we shouldn't remove it from
ActiveExecutions
, and instead retain it to be able to use the response-promise and the startedAt timestamp.Related Linear tickets, Github issues, and Community forum posts
CAT-545
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)