Well, the truth is that I kept the best surprise for this post. It is simply so good, it deserves a post of its own…
So, what am I talking about?
Today I am talking about the option to investigate a flow which already ran in Central, by initiating the same flow, with the same run values, in the Studio Debugger!
Closer look at a typical use case
Let’s say that the Administrator complains that a specific flow run has failed. This is a big flow. You cannot immediately find the reason why it failed, and you do not see it clearly enough in the Central logs. Furthermore, you find it hard to reproduce the issue.
How is it done?
As an example, let us rerun the “Add selected Module From Forge” flow which appears in the screenshot below:
We will copy the run id of the relevant run to the clipboard, to be used in Studio later on.
As a provisioning addict for 20 years, I was involved in projects in EMEA and the US as engineer, solution architect and project manager. In the last 2 years I'm in the Operations Orchestrations Community Assistance Team in HP Software R&D.