[CoE Starter Kit - BUG] I found that the flows were marked as deleted in CoE

[hilda-hk]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

Hi, I have found that there are some flows in Flow table (admin_flow) have marked as deleted. After checking the flows, those deleted flows were deleted on the date.

Expected Behavior

Only the flows deleted by users will be classified as deleted flows

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.37

What app or flow are you having the issue with?

not sure. After checking, I am wondering if CoE flow CLEANUP HELPER - Check Deleted v4 (Cloud Flows) removed the flow which are not published or not.

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Sorry I'm not quite following.

1. Are these flows deleted from the tenant? Or do they still exist?
2. If they still exist, are they unpublished flows? Meaning are they in a solution and never having been turned on?

[hilda-hk]

Hi Jenefer, sorry for my unclear statement. Below are my comments:

1. In CoE, the flows are marked as deleted, but the flows actually do exist.
2. I took one flow as an example. The flow marked as deleted on 15 Sept in CoE, but the flow ran 4 days ago.

Thank you.

[hilda-hk]

Hi Jenefer, may I know is there any clue on this issue? The unpublished flows do not mean deleted flow, so it should not be marked as deleted in the CoE inventory.

[Jenefer-Monroe]

We do not track unpublished flows in the kit because the GUID associated with them is not constant and will change over time.
We do have a backlog item to do work to incorporate them but its not yet funded.
When the product team first shipped the ability to return unpublished flows it was done in a way that accidently put them in the kit and we fast followed to clean them.

I'm not sure that is what is happening with you but let's go ahead and put that down before we continue.

Please go find a flow that is marked deleted but which does still exist in the tenant, find that in the Flow table and add the following column to see if its marked Flow Is Published as true or false.

If you find a case where

• flow still exists in tenant
• flow is marked deleted
• flow is marked as published

Then let me know and we can continue to investigate.

[hilda-hk]

Yes I have the examples meet the above three conditions.

[Jenefer-Monroe]

Great thank you.
Please take the environment and flow GUIDs for one of these and run it through the following flow: SYNC HELPER - Cloud Flows

Open the resulting run and see what happens

[oburgoscr]

Hi, I'm experiencing the same issue.
Is there any update on what is happening and how to resolve it?

[Jenefer-Monroe]

Hello this was left open accidently. Issues like this typcially mean there is somethign mis configured.
Please do post a new issue and someone will triage for you.

[oburgoscr]

Hi! I opened 2 GitHub issues and after a few minutes I got three emails like these: * [microsoft/coe-starter-kit] Run failed: Auto Assign Issues to Projects - main (5925b26) * [microsoft/coe-starter-kit] Run cancelled: Sync issue to Azure DevOps work item - main (5925b26) * [microsoft/coe-starter-kit] Run failed: Sync issue to Azure DevOps work item - main (5925b26) It seems the auto assign job failed. Can someone pick up any of these tickets manually? #9498 #9506 Regards, Oliver

…

________________________________ From: Jenefer Monroe ***@***.***> Sent: Monday, January 13, 2025 4:54 PM To: microsoft/coe-starter-kit ***@***.***> Cc: Burgos, Oliver ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/coe-starter-kit] [CoE Starter Kit - BUG] I found that the flows were marked as deleted in CoE (Issue #9079) Closed #9079<#9079> as completed. — Reply to this email directly, view it on GitHub<#9079 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2ANYKDHE5K6HC2AOMSMPOT2KQ7ZRAVCNFSM6AAAAABPLQRSPCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVHEYTIMJUGA3DKNQ>. You are receiving this because you commented.