[X] I had searched in the issues and found no similar issues.
What happened
Task type：Shell
Execution policy: Serial wait
Trigger API: executors/start-process-instance，with startParams
After the API interface is triggered twice in a row, the first task instance executes normally, but when the second task instance changes from serial wait to serial recovery, the variables carried by the task instance are lost
You can reproduce it like I did：Two shell-type tasks are defined in a workflow and each task sleeps for a few seconds. The main observation is the variable condition after the state switch of the second task instance
Anything else
This is the first time I have written an Issue. Please point out any ambiguities (。・＿・。)ﾉI’m sorry~
Search before asking
What happened
Task type：Shell Execution policy: Serial wait Trigger API: executors/start-process-instance，with startParams After the API interface is triggered twice in a row, the first task instance executes normally, but when the second task instance changes from serial wait to serial recovery, the variables carried by the task instance are lost
trigger url：http://xxxxxxx:12345/dolphinscheduler/projects/12083148079392/executors/start-process-instance?failureStrategy=END&processInstancePriority=MEDIUM&warningType=NONE&projectCode=12083148079392&processDefinitionCode=14285688004928&scheduleTime=""&startParams={"start_date":"2024-07-01","end_date":"2024-07-14","review_filter":"25031363,31009374","level":"REPORT_LEVEL_ADVERTISER"}
Two consecutive triggers:
Variable waiting for the second instance:
Serial recovery:
Runtime variable:
Completed state:
What you expected to happen
In serial mode, variables are not lost
How to reproduce
You can reproduce it like I did：Two shell-type tasks are defined in a workflow and each task sleeps for a few seconds. The main observation is the variable condition after the state switch of the second task instance
Anything else
This is the first time I have written an Issue. Please point out any ambiguities (。・＿・。)ﾉI’m sorry~
Version
3.1.x
Are you willing to submit PR?
Code of Conduct