dolphinscheduler icon indicating copy to clipboard operation
dolphinscheduler copied to clipboard

When sub_process executes a subtask, an error occurs when passing parameters

Open leachli opened this issue 1 year ago • 2 comments

Search before asking

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

What happened

任务节点中有参数传递时,无法使用重跑功能

What you expected to happen

执行主任务A,A 任务流中有 sub_process 任务B ,任务B 流程中有 B1->B2,其中B1输出参数 传递到B2,主任务A 运行类型为"启动工作流时",所有任务执行正常,如果触发重跑,则任务会执行失败,失败节点在参数传递节点,如图: image

How to reproduce

执行主任务A,A 任务流中有 sub_process 任务B ,任务B 流程中有 B1->B2,其中B1输出参数 传递到B2,主任务A 运行类型为"启动工作流时",所有任务执行正常,如果触发重跑,则任务会执行失败,失败节点在参数传递节点,如图: image

Anything else

No response

Version

3.2.x

Are you willing to submit PR?

  • [X] Yes I am willing to submit a PR!

Code of Conduct

leachli avatar Apr 12 '24 01:04 leachli

Search before asking

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

What happened

When there are parameters passed in the task node, the rerun function cannot be used.

What you expected to happen

Execute main task A. There is sub_process task B in the task flow of A. There is B1->B2 in the process of task B. The output parameters of B1 are passed to B2. The running type of main task A is "when starting the workflow". All tasks execute normally. If rerun is triggered, the task will fail to execute, and the failure node is the parameter passing node, as shown in the figure: image

How to reproduce

Execute main task A. There is sub_process task B in the task flow of A. There is B1->B2 in the process of task B. The output parameters of B1 are passed to B2. The running type of main task A is "when starting the workflow". All tasks execute normally. If rerun is triggered, the task will fail to execute, and the failure node is the parameter passing node, as shown in the figure: image

Anything else

No response

Version

3.2.x

Are you willing to submit PR?

  • [X] Yes I am willing to submit a PR!

Code of Conduct

github-actions[bot] avatar Apr 12 '24 01:04 github-actions[bot]

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.

github-actions[bot] avatar May 16 '24 00:05 github-actions[bot]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

github-actions[bot] avatar May 23 '24 00:05 github-actions[bot]