<?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: Help Recovering Closed KQL Query Tabs in Fabric in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704183#M9518</link>
    <description>&lt;P&gt;you are correct here&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fabric does not auto-save queries in progress unless explicitly saved by the user. This applies to both executed and unexecuted queries.&lt;BR /&gt;• The “Queries auto-save” feature mentioned in Kusto Explorer does not exist in Fabric’s KQL queryset interface.&lt;/P&gt;</description>
    <pubDate>Thu, 22 May 2025 21:48:18 GMT</pubDate>
    <dc:creator>nilendraFabric</dc:creator>
    <dc:date>2025-05-22T21:48:18Z</dc:date>
    <item>
      <title>Help recovering closed KQL query tabs in a Queryset</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704162#M9514</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;My team and I are working with a KQL database in Microsoft Fabric, specifically querying data through a queryset. Unfortunately, I accidentally closed an important tab that contained KQL significant queries to our development process.&lt;/P&gt;&lt;P&gt;I've been checking the Fabric documentation, but haven’t found anything helpful regarding recovering a closed tab or previously written queries. Does anyone know if there's a way to recover them?&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 21:23:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704162#M9514</guid>
      <dc:creator>KerenLopez</dc:creator>
      <dc:date>2025-05-22T21:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: Help Recovering Closed KQL Query Tabs in Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704176#M9515</link>
      <description>&lt;P&gt;hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/1231882"&gt;@KerenLopez&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All queries executed against a Kusto database are logged in the query history. You can access this by running the following KQL command in your Fabric environment:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;.show queries | where StartedOn &amp;gt; ago(2h)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Adjust the time window as needed to filter for your recent queries.&lt;BR /&gt;• This allows you to recover the actual query text, even if the tab itself is lost&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 21:23:14 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704176#M9515</guid>
      <dc:creator>nilendraFabric</dc:creator>
      <dc:date>2025-05-22T21:23:14Z</dc:date>
    </item>
    <item>
      <title>Re: Help Recovering Closed KQL Query Tabs in Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704179#M9517</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/913195"&gt;@nilendraFabric&lt;/a&gt;,&amp;nbsp;&lt;BR /&gt;Thanks for your reply!&lt;/P&gt;&lt;P&gt;Just to confirm, does that mean that any part of the code that was written but not executed is permanently lost? If so, that's quite concerning.&lt;/P&gt;&lt;P&gt;Honestly, I’m surprised that Fabric doesn’t offer any kind of auto-save or version history for queries within a queryset. Considering how easy it is to accidentally close a tab or lose progress, it feels like an important feature that should be built in by default.&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 21:33:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704179#M9517</guid>
      <dc:creator>KerenLopez</dc:creator>
      <dc:date>2025-05-22T21:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help Recovering Closed KQL Query Tabs in Fabric</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704183#M9518</link>
      <description>&lt;P&gt;you are correct here&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fabric does not auto-save queries in progress unless explicitly saved by the user. This applies to both executed and unexecuted queries.&lt;BR /&gt;• The “Queries auto-save” feature mentioned in Kusto Explorer does not exist in Fabric’s KQL queryset interface.&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 21:48:18 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Help-recovering-closed-KQL-query-tabs-in-a-Queryset/m-p/4704183#M9518</guid>
      <dc:creator>nilendraFabric</dc:creator>
      <dc:date>2025-05-22T21:48:18Z</dc:date>
    </item>
  </channel>
</rss>

