SeaFish903 opened a new issue, #16318:
URL: https://github.com/apache/dolphinscheduler/issues/16318

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) 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
   
   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:
   
![1](https://github.com/user-attachments/assets/e26d9a82-ce37-4280-8d91-56cc408eee58)
   
   Variable waiting for the second instance:
   
![2](https://github.com/user-attachments/assets/0ae2feb2-3d20-4faa-a307-c2c951f77519)
   
   Serial recovery:
   
![3](https://github.com/user-attachments/assets/2483b77d-de99-482f-962b-380bd04865fc)
   
   Runtime variable:
   
![4](https://github.com/user-attachments/assets/245eceb8-c3c4-43d6-9d99-e4087b26b6db)
   
   Completed state:
   
![5](https://github.com/user-attachments/assets/9898e307-995a-4460-8894-5f38905cd389)
   
   
   
   ### 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?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to