[Bug] [dolphinscheduler-server] param lost when execute failed task

[zwZjut]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

param lost when execute failed task
branch 2.0.5 && dev

What you expected to happen

param will not lost when execute failed task

How to reproduce

create processDefinition test
create task A set parameter a and set OUT
create task B dependent task A and use parameter a; do something let task B 100% failed
run processDefinition test and server will create processInstance test_xxxx
find test_xxxx in list and execute failed tasks, when it is failed, open the task log :
"setSqlParamsMap: No Property with paramName: a is found in paramsPropsMap of task instance with id"

Anything else

No response

Version

2.0.5

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

[Tianqi-Dotes]

@zwZjut hi, I cannot reproduce, could you provide your process definition script here?
I passed a param from task A to task B and set task B timeout failure, but in my test, task B can reach the param value from task A.

[zwZjut]

if you still cannot reproduce, connect me in wechat by name of HY in ds group

[zwZjut]

you can also see difference between two tasks in meta data

[Tianqi-Dotes]

dev part code is fine， you can try dev

[zwZjut]

dev part code is fine， you can try dev

will you cherry-pick to 2.0.6 ? is it easy to fix ?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[zwZjut]

this problem exists in 2.0.x