Help recovering closed KQL query tabs in a Queryset

[KerenLopez]

Hi everyone,

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.

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?

Any help would be greatly appreciated!

Thanks in advance.

[nilendraFabric · Accepted solution]

hi @KerenLopez 

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:

.show queries | where StartedOn > ago(2h)

Adjust the time window as needed to filter for your recent queries.
• This allows you to recover the actual query text, even if the tab itself is lost

[KerenLopez · Accepted solution]

Hi @nilendraFabric, 
Thanks for your reply!

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.

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.

[nilendraFabric · Accepted solution]

hi @KerenLopez 

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:

.show queries | where StartedOn > ago(2h)

Adjust the time window as needed to filter for your recent queries.
• This allows you to recover the actual query text, even if the tab itself is lost

[KerenLopez · Accepted solution]

Hi @nilendraFabric, 
Thanks for your reply!

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.

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.

[nilendraFabric · Accepted solution]

you are correct here

Fabric does not auto-save queries in progress unless explicitly saved by the user. This applies to both executed and unexecuted queries.
• The “Queries auto-save” feature mentioned in Kusto Explorer does not exist in Fabric’s KQL queryset interface.