[ALM Accelerator - BUG]: Renaming a flow causes Activate Flows step in pipeline to fail

[manuelap-msft]

Describe the issue

We've renamed a flow in our solution, this flow is no longer listed in the "Flows" page of the deployment settings, however it looks like the Activate Flows step picks this flow up and then fails as it can't activate it.

The flow name changed from
Admin | Sync Template v3 (Apps) to Admin | Sync Template v4 (Apps)

Here's what we see:
First, the flow seems to be added to the activation collection

Then, the activation fails

Expected Behavior

No response

What component are you experiencing the issue with?

ALM Accelerator Pipelines

What solution version are you using?

latest

Steps To Reproduce

No response

Anything else?

This is not blocking us, just thought I'd mention it.

[mikefactorial]

Thanks for reporting @manuelap-msft. Glad to know it's not blocking, but feel free to let me know if you need anything related to this issue in the short term :)

[RajeevPentyala]

@manuelap-msft Regarding the flow rename issue, we found out that the flow "Admin | Sync Template v3 (Apps)" was not deleted on 'pctools-test'. We executed the pipeline with the 'Upgrade' option, which successfully removed the outdated flows and activated the flows successfully. FYI @mikefactorial

[CoEStarterKitBot]

@manuelap-msft This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.