wcmolin commented on issue #18604:
URL: 
https://github.com/apache/dolphinscheduler/issues/18604#issuecomment-5490449316

   I have opened #18608 with an alternative fix.
   
   The force-success API already persists the `FORCED_SUCCESS` state and end 
time before workflow recovery. Therefore, the recovery state action should not 
update the completed task instance again.
   
   The fix skips the redundant success-state persistence while retaining the 
inherited workflow continuation logic, including variable-pool merging and 
downstream task triggering.
   
   A unit test verifies that the task remains `FORCED_SUCCESS` and workflow 
execution continues. The related reactor build and test pass with JDK 8.
   


-- 
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