<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Bizarre and long running DF refreshing in Dataflow</title>
    <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3433505#M841</link>
    <description>&lt;P&gt;Through a support ticket, I found out a column in a source table contained an unsupported data type. The surprising part is that this table had nothing to do with the dataflow. It got me thinking:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Does the dataflow refresh look at all source tables in the lakehouse, even those not used?&lt;/P&gt;&lt;P&gt;2. How much data can a dataflow handle? In terms of MB/GB? In terms of the final number of rows and columns?&lt;/P&gt;</description>
    <pubDate>Fri, 15 Sep 2023 19:56:19 GMT</pubDate>
    <dc:creator>ebjim</dc:creator>
    <dc:date>2023-09-15T19:56:19Z</dc:date>
    <item>
      <title>Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3399220#M742</link>
      <description>&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;I like to know from other users if you have exprience anything similar to what the screenshot shows.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- The first attempt (success) occurred after I made some changes to the dataflow and lakehouse table.&lt;/P&gt;&lt;P&gt;- The second attempt was triggered by running the DF (no mods) in a data pipeline.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- The third attempt was manually triggered. DF is unchanged.&lt;/P&gt;&lt;P&gt;- The fourth attempt was manually triggered. DF is unchanged.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The situation is downright ridiculous, with no way to terminate refreshes and no way of knowing how long it's going to keep going in a endless spiral.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Aug 2023 13:44:37 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3399220#M742</guid>
      <dc:creator>ebjim</dc:creator>
      <dc:date>2023-08-25T13:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3399887#M745</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="582610" data-lia-user-login="ebjim" class="lia-mention lia-mention-user"&gt;ebjim&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Thanks for using the Fabric community.&lt;/P&gt;
&lt;P&gt;I am in agreement with you that its does not look right . The same DF takes 8 hrs and then fails and in the best case scenario it completes in 4 mins .&amp;nbsp; I think we need to check if there are other workloads running which is taking the capacity units&amp;nbsp; ,please do read &lt;A href="https://learn.microsoft.com/en-us/fabric/get-started/fabric-trial#capacity-units" target="_self"&gt;this &lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If its not related to to CU issues , I will suggest you to work with the MS support as they can dig more on this .&amp;nbsp;&lt;BR /&gt;Thanks&lt;BR /&gt;HImanshu &lt;/P&gt;</description>
      <pubDate>Fri, 25 Aug 2023 21:04:22 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3399887#M745</guid>
      <dc:creator>HimanshuS-msft</dc:creator>
      <dc:date>2023-08-25T21:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3399934#M747</link>
      <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="538677" data-lia-user-login="HimanshuS-msft" class="lia-mention lia-mention-user"&gt;HimanshuS-msft&lt;/a&gt;&amp;nbsp;Thank you for your feedback. As a trial user, I am aware of the limits of assigned resources. That is why I only refresh one DF at a time. What I find troubling is that there seems to be a point of complexity within a DF, from which refreshing totally breaks down (like a cliff dropoff). Often times, I am the only one using the trial account, so it's not a high load situation. I would still encourage the Fabric group at Microsoft to resolve such issues.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Aug 2023 21:35:05 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3399934#M747</guid>
      <dc:creator>ebjim</dc:creator>
      <dc:date>2023-08-25T21:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3406400#M763</link>
      <description>&lt;P&gt;&lt;A href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/582610" target="_self"&gt;&lt;SPAN class=""&gt;ebjim&lt;/SPAN&gt;&lt;/A&gt;&amp;nbsp;I am having the exact same issue - me being the only one using the capactiy and having only one workflow running. Would love to hear any fixes you come up with &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="538677" data-lia-user-login="HimanshuS-msft" class="lia-mention lia-mention-user"&gt;HimanshuS-msft&lt;/a&gt;&amp;nbsp;- could this be a compute issue? Sometimes if I have a flow running it gets locked for 8 hours as well, and then I am also unable to work with any other resources in Fabric.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 10:48:23 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3406400#M763</guid>
      <dc:creator>DataPne</dc:creator>
      <dc:date>2023-08-30T10:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3406709#M765</link>
      <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="603905" data-lia-user-login="DataPne" class="lia-mention lia-mention-user"&gt;DataPne&lt;/a&gt;&amp;nbsp;I have no fixes to offer up. Since we as users cannot even terminate any refesh, complaining to MSFT is the only recourse I can think of. Because we get errors that just seem 'way out there', I suspect there are memory leaks or caching problems behind the scenes that have yet to be addressed. When I was using Azure, nothing of this sort happened.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 13:35:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3406709#M765</guid>
      <dc:creator>ebjim</dc:creator>
      <dc:date>2023-08-30T13:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3433505#M841</link>
      <description>&lt;P&gt;Through a support ticket, I found out a column in a source table contained an unsupported data type. The surprising part is that this table had nothing to do with the dataflow. It got me thinking:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Does the dataflow refresh look at all source tables in the lakehouse, even those not used?&lt;/P&gt;&lt;P&gt;2. How much data can a dataflow handle? In terms of MB/GB? In terms of the final number of rows and columns?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 19:56:19 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3433505#M841</guid>
      <dc:creator>ebjim</dc:creator>
      <dc:date>2023-09-15T19:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3439012#M859</link>
      <description>&lt;P&gt;Hi - we invested a lot of time into porting very stable Gen1 dataflows over to Gen2 dataflows as the concept is great - however they just are not very stable at the moment and the performance is poor at best.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have architected a solution by using our old gen1 dataflows to load to datamarts and then using the copy activity in data pipelines to move the data into our Warehouse.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If youa re interested to know more let me know&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2023 23:50:46 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3439012#M859</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-09-19T23:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: Bizarre and long running DF refreshing</title>
      <link>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3440205#M861</link>
      <description>&lt;P&gt;Anonymous&lt;/a&gt;&amp;nbsp;I appreciate your kind offer. Right now, I have a created a plan B using Azure, which I know will work. So, for now I would say that I can move forward in some way, but I'll let you if I need to take a look at your gen1 solution. Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2023 15:05:29 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Dataflow/Bizarre-and-long-running-DF-refreshing/m-p/3440205#M861</guid>
      <dc:creator>ebjim</dc:creator>
      <dc:date>2023-09-20T15:05:29Z</dc:date>
    </item>
  </channel>
</rss>

