Hi,
Recently I moved to version 1.39.0 from 1.16.0 and I noticed a weird thing:
In version 1.16.0 (and before) retried failed executions can be retried again:
But in 1.39.0 this is not the case - Only the original failed execution can be retried:
I wonder why this behavior changed?
It looks like your topic is missing some important information. Could you provide the following if applicable.
Hi @jellybean
Yes, this was a conscious decision we implemented in release version 1.36.2
We wanted that the retry button should be shown only for errored executions that don’t already have a successful retry.
Thanks @ria ,
Take a look at the second screenshot I provided.
Only first failed execution has retry button. The other “failed” ones don’t have retry button.
Let’s imagine this flow: A → B → C → D → E → F
Suppose first execution would throw error at B node. I would retry it and it passes the B node but throw another error at E node.
But the second execution doesn’t have retry button. It means I can’t retry the execution at E node. Only the first execution (B node) can be retried.
Therefore B, C and D nodes are getting run again. Which doesn’t make sense.
Maybe I got it wrong.
Could you help?
Hello? anyone?
Hi @ria
Could you please look into this issue? I’m encountering the same problem where my first execution failed at the second node of a six-node flow. When I retried, the second execution also failed, but this time at the sixth node. Currently, I don’t have the option to retry the second execution, and I’d prefer not to restart from the beginning. I want to retry only the sixth node of the latest execution. Can you help with this? Thanks
Hi all,
very sorry for the delayed response!
We had a look internally and were able to reproduce the issue. We have started a ticket for it and will update about the progress here.
Thanks for your patience and your valuable feedback 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
