'WorkflowNodeExecution' object has no attribute 'update_from_mapping' #13994

Closed
opened 2026-02-21 19:14:58 -05:00 by yindo · 5 comments
Owner

Originally created by @344310362 on GitHub (May 19, 2025).

Originally assigned to: @laipz8200 on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.4.0

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

when run chatflow,ui no response,and 了 api server has error log:

'WorkflowNodeExecution' object has no attribute 'update_from_mapping'

Image

Image

code branch :main latest

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @344310362 on GitHub (May 19, 2025). Originally assigned to: @laipz8200 on GitHub. ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.4.0 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce when run chatflow,ui no response,and 了 api server has error log: 'WorkflowNodeExecution' object has no attribute 'update_from_mapping' ![Image](https://github.com/user-attachments/assets/58357b78-4691-4340-b26e-c9a91c0fba4a) ![Image](https://github.com/user-attachments/assets/34ecd2ab-0cd4-470a-baee-fac52e31c817) code branch :main latest ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:14:58 -05:00
yindo closed this issue 2026-02-21 19:14:58 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (May 19, 2025):

Hello @344310362! I'm Dosu, here to assist you with any bugs or questions you might have while you wait for a human maintainer. Let's tackle this together!

The error you're encountering is due to the WorkflowNodeExecution object not having the update_from_mapping method. This method is defined in the NodeExecution class, not in WorkflowNodeExecution. To resolve this issue, ensure that the object you are working with is an instance of the NodeExecution class, which does have the update_from_mapping method defined [1].

You may need to check where the object is instantiated and ensure it is created correctly as a NodeExecution instance. If the object is supposed to be a NodeExecution but isn't, you might need to adjust the instantiation logic in your code to use the correct class.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (May 19, 2025): <!-- Greeting --> Hello @344310362! I'm [Dosu](https://dosu.dev), here to assist you with any bugs or questions you might have while you wait for a human maintainer. Let's tackle this together! <!-- Answer --> The error you're encountering is due to the `WorkflowNodeExecution` object not having the `update_from_mapping` method. This method is defined in the `NodeExecution` class, not in `WorkflowNodeExecution`. To resolve this issue, ensure that the object you are working with is an instance of the `NodeExecution` class, which does have the `update_from_mapping` method defined <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/entities/node_execution_entities.py)</sup>. You may need to check where the object is instantiated and ensure it is created correctly as a `NodeExecution` instance. If the object is supposed to be a `NodeExecution` but isn't, you might need to adjust the instantiation logic in your code to use the correct class. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ce6cc78f-2550-434e-b74f-25a0261c4480?feedback_type=other)</sup>
Author
Owner

@344310362 commented on GitHub (May 19, 2025):

I haven't modified any source code. I just pulled the latest main branch code to run

Image

@344310362 commented on GitHub (May 19, 2025): I haven't modified any source code. I just pulled the latest main branch code to run ![Image](https://github.com/user-attachments/assets/22afcc6a-dfc0-4286-8d78-d0ebc90165dd)
Author
Owner

@ft4710403 commented on GitHub (May 19, 2025):

我也和你一样,查了几个小时了擦。。

Image

@ft4710403 commented on GitHub (May 19, 2025): 我也和你一样,查了几个小时了擦。。 ![Image](https://github.com/user-attachments/assets/e77399f0-9d99-4753-843d-de2d17edffaa)
Author
Owner

@bowenliang123 commented on GitHub (May 19, 2025):

Hi All, I have encountered the same problem. And as for the quick fix, reverting to the 1.4.0 release tag is the best way to avoid it.

@bowenliang123 commented on GitHub (May 19, 2025): Hi All, I have encountered the same problem. And as for the quick fix, reverting to the 1.4.0 release tag is the best way to avoid it.
Author
Owner

@bowenliang123 commented on GitHub (May 19, 2025):

also cc @laipz8200 as the author of #19430

@bowenliang123 commented on GitHub (May 19, 2025): also cc @laipz8200 as the author of #19430
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#13994