I've got a simple flow that will update a custom status on a NetSuite sales order based on the result of the preceding Import.
I've configured the Import to continue to the next step so it will update the sales order to an error status in the event of a failure. The problem is that when the issue has been resolved in the destination system and the error retried, it seems to skip the following step. I recall learning this before and that the explanation is that the flow already successfully ran the following steps so it won't run them again. I'm sure there are many use cases where this is desirable, but likewise there are used cases where it is not, like mine!
The only idea I have is to duplicate the update node so there are two of them; 1 with an import filter checking for Success and the other filtering to fail. That way, theoretically, if the retry succeeds it would still run the success node. That is a pretty ugly solution though.
Has anyone come up with a good pattern to deal with this scenario?
Celigo, do you have an enhancement to give more control over how retry will behave? Perhaps we can configure the "record fail" setting to "Re-run subsequent steps" or alternatively, add an option to steps to "run on retry"? I'm sure there are other, better solutions.