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

   ### 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
   
   When I set the time condition of the dependency task node to "this week", 
the workflow did not execute properly.
   - I configured a dependency task node that relies on the successful 
execution of another workflow, with a time condition of "this week".
   
![image](https://user-images.githubusercontent.com/62830983/224958397-4e8f87b5-22b6-40fd-86b8-ba9455cdaf54.png)
   - However, in reality, the other workflow has already executed successfully, 
but the dependency task is still in progress.
   
![image](https://user-images.githubusercontent.com/62830983/224958775-d265590f-5b17-49c8-8d30-abf053ba94b4.png)
   
   
   
   
   ### What you expected to happen
   
   When I configure a time condition for a dependency node as "this week", and 
another workflow has already executed successfully this week, this dependent 
task should be executed normally.
   
   ### How to reproduce
   
   I have configured two workflows, and one of them has a dependency task node 
that relies on the successful execution of the other workflow with a time 
condition set for this week.
   
   However, in reality, the other workflow has already executed successfully, 
but the dependent task is still in progress.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   dev
   
   ### Are you willing to submit PR?
   
   - [X] 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