Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Retry workflow from task inside fork #310

Open
DDorian13 opened this issue Nov 15, 2024 · 0 comments
Open

[BUG] Retry workflow from task inside fork #310

DDorian13 opened this issue Nov 15, 2024 · 0 comments

Comments

@DDorian13
Copy link

Describe the bug
Inside the fork when you retry the workflow from a step, the separate branches will be deleted too but will not run later.
As the attached image, every part of the fork has built the same way, a step followed by a sub workflow. After the initial execution the Sequence numbers will be as shown in the picture (the steps will be 1, 2, 3 and sub workflows 4, 5, 6) which results that the rerun logic will filter out everything after the retried step (Seq 2). This is totally invalid as inside the fork the "next" branches has nothing to do with the original step (Step 2 in this case)

Details
Conductor version: 3.21.5

To Reproduce
I cannot share the exact workflow because it contains confidental information but attached a screenshot which clearly describes the schema of the workflow.
After running the workflow you should retry the workflow from the task Step 2 which I have done through the API.

Expected behavior
Only the selected branch should be restarted and the others should not be reseted. In this case Step 2 and Sub Workflow 2

Screenshots
image

@DDorian13 DDorian13 changed the title Bug: Retry workflow from fork resets invalid parts too [BUG] Retry workflow from task inside fork Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant