How to "undelete" flows marked as deleted in ByoDL environment #7511
Comments
shoffma1
added
coe-starter-kit
|
This should happen automatically with the dataflow refreshes. Can you please show a screenshot of the dataflows to see if they are passing? |
|
Hello @Jenefer-Monroe, we are also getting this issue. Flows, Apps and environments are being marked for deletion and most of the flow are under the "Deleted flows/apps/environment/AI Models" view in the Admin View. I was able to observe that this is happening after the scheduled refresh of dataflows. Once I do a manual refresh of the flow - the flows are again available and are removed from the deleted view. Here is an example of our default environment under the "Deleted Environments Review" View.
|
|
@niwrejim21 can you please share a screenshot like this? |
This is my view ... |
|
|
|
I'm not sure how you got into this state, but if you go and delete records in the dataflow history table back to when you saw this issue happen, that should clear it up. |
Thanks for this. Would there perhaps be a more automated way to delete all rows from this table, as I have no idea when the issue started. |
|
@Jenefer-Monroe , it happened again today - it seems that this is an intermittent issue. No dataflow failed during the scheduled refresh but some of the resources including our default environment got marked for deletion again. Yesterday, the scheduled refresh worked fine. To be able to fix it, I had to do a refresh of the dataflows again. |
|
We did create a more automated way to do this in the Feb release. You'll now see a button which lets you delete back as far as you want |
|
@niwrejim21 I'm not sure what you mean by marked for deletion. Do you mean they are marked as deleted? |
|
This was last week - our default environment is under the deleted view:
This is today:
Please also notice the number of Apps between the two snapshots (from 9k+ to 250). The missing apps are now under the Deleted Apps view and have a "app deleted on" date of 1/29/2024. Those apps are not actually deleted and if I run a manual refresh of the makers dataflow - it will eventually be corrected.
|
|
Please go to the Admin Command Center > CoE Flows > Inventory. Validate that all flows are turned on and that there are no unmanaged layers as shown here. |
|
ok another person posted the question and it pointed me to the issue. Please see #7562 (comment) for how to locally resolve. And let me know! |
Not sure this will work for us, as this particular flows is not "On", and gives an error trying to do so. Sorry, I can't keep straight which flows should be on or off for the ByoDL solution vs the older. |
|
No problem. The instructions for the workaround are for a Dataflow. So if you are using DAta Export that one should be on. The issue is in the Dataflow (which brings the default ent back as default-abc123.... instead of Default-abc123...). So regardless of if you are using v3 or v4 of the check deleted cloud flow system, you would be impacted. |
|
@Jenefer-Monroe - confirming that the fix resolved our issue as well. Appreciate all the help!!! |
|
After applying the above code to our dataflow, and activating the Admin sync flow, the general number of flows seems to be correct, however all of the data is now missing in the active flows view, or when clicking into one of the flows from there ... |
|
What do you mean by this: |
Currently all of our v4 Cleanup flows are off. I had activated this one for a short time: CLEANUP - Admin | Sync Template v4 (Check Deleted)CLEANUP - Admin | Sync Template v4 (Check Deleted) |
|
This is written to from another dataflow and mine is working as are the other folks who did the workaround. So I think there may be something unique to your envt.
|
|
As of this morning none of these flows are listed at all, even after removing the "Flow Deleted" filter. 
|
|
If you go look at the flow table itself, instead of this roll up number, do you see flows in default? |
|
No, nothing from the default environment. It almost seems like our "service" account had lost access to that environment, but it does have the "System Administrator" role there, and the "Power Platform Admin" role in Entra, though it is from a group. |
|
Can you go see if the file is present in the Data Export storage account?
|
|
Yes, our Default env is in the data export. In fact, the power bi report is coming through fine with all of our flows from that environment. |
|
Great. Please view the dataflows. |
|
Correct, only the "CoE BYODL Makers" dataflow has a "Next refresh" that is not "N/A". And the refresh history for "CoE BYODL Flows" is showing success as far back as that goes (12/18/2023). |
|
great, now please note the last modified date for the Default-abc... record for flows Delete the records from the DataflowRefreshHistories table back through that date Open the flow CoE BYODL Flows dataflow and see if you find the default envt flows in there, and if the name of the environment has the upper or lower casing for the word default: Default-abc... or default-abc... |
|
Our data export file for our default environment has the current date (6-Feb). I did go ahead and delete today's refresh history items regardless. Not sure if this is relevant, but we have two dataflows uploaded to powerbi ... one is the january release, which is showing our Default environment, with a capital D. The older dataflow shows the default environment with a lowercase d. When I look from the "make.powerapps.com" portal, I'm getting the message, "This table has no rows". 
|
|
We aren't doing anything with the PBI Dataflows here. The change above is not neeed for them. |
|
Yes, confirming only working with the Dataflows in the solution. 
Just not sure why we are now seeing zero flows, for any environment here. 
|
|
I've set up to try and repro locally, although I do not yet. Will let you know what I find next week |
|
ok I do not repro this issue. it could be that the local fix isnt applied correctly, or something else has changed in the build. |
|
This should probably be another issue report, but running the upgrade wizard after installing the 4.23 Core components solution, getting this on the first page after the modal windows. 
|
|
After installing the 4.23 Core components, I was able to delete all the DataFlowRefreshHistory items. Thank you for that option to delete all! Now I am getting this error, even after configuring the connections, etc., in the DataFlows ... this is the BYODL Environments dataflow ... 
We do now have our flows populating, but still have a couple that are blank ... 
|
|
This means that the maker is not in the inventory. This typically happens when you have set the next reresh on all the dataflows instead of just the maker one. |
|
FYI, after our daily refresh(es) completed this morning, we have zero blank flows showing, and the correct number of flows from our default environment. I think we're good at this point. Thanks for your help! |
|
Wonderful news! I'm still testing a little more and have a few other folks testing as well so ill hold this till early next week and then hopefully close out feeling good about the March release :) Thanks for your help! |
|
ok this is looking good for March release. |
Does this question already exist in our backlog?
What is your question?
From before the January update, some 2000 of our flows from our main environment have been marked as deleted. Though they show up in the PowerBI report now, they are not in the default view in the Admin app.
How can we get remove the "marked as deleted"?
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.22
What app or flow are you having the issue with?
Not sure
What method are you using to get inventory and telemetry?
Data Export
AB#2105
The text was updated successfully, but these errors were encountered: