GIT integration with Lakehouse not working this morning

A fix for this is being investigated by Fabric engineers. I got a EOD 24th as a date from the support. 

Is no one else facing the issue? I am unable to sync or update any workspace which has a lakehouse in it. I need the lakehouse and warehouse in the same workspace to be able to run cross database queris during data transformation. I am sure others may be using the same set-up.

We have the same issue now in Sweden it seems, has anyone created a ticket regarding this i powerapps and got it resolved without waiting out 1 day? 

Same issue for the North Europe zone. When trying to update a workspace from Git using PowerShell, we get the error ""InvalidDefinitionFormat ,message":"Requested item definition format is invalid".

When trying to sync a new empty workspace with a Fabric repo containing a Lakehouse, we get the error "Git_InvalidResponseFromWorkload".

I am experiencing exactly the same issue, I am unable to commit a lake house resource to GitHub or azure devops. Hopefully this is fixed promptly.

Hi Amit_K,

Thank you for reaching out to Microsoft Fabric Community.

As we haven’t heard back from you, we wanted to kindly follow up to check if the issue is resolved. or let us know if you need any further assistance!
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,

Anjan Kumar Chippa

Hello, I do have the same issue, also only with the Fabric Lakehouses.

When updating via Git Sync : 

<plaintext>
Error response: {
"errorCode": "Git_InvalidResponseFromWorkload",
"message": "An error occurred while processing the operation",
"relatedResource": {
"resourceId": "xxx",
"resourceType": "Lakehouse"
}
}
</plaintext>

I am using a mix of these PS scripts, for polling the long operation when syncing :

fabric-samples/features-samples/git-integration/GitIntegration-UpdateFromGit.ps1 at main · microsoft/fabric-samples · GitHub

fabric-samples/features-samples/fabric-apis/LongRunningOperation-Polling.ps1 at main · microsoft/fabric-samples · GitHub

And on the GUI, when clicking on Update all (only a Lakehouse in the change list) , I got the following pop up :

<plaintext>Title: Operation Blocked

Content: We couldn't complete this request because the items in the following list have a reserved name. Try again later.
</plaintext>

Previously working Fabric workspaces with Lakehouses integrated to Azure DevOps Git repos are failing with the 'Something went wrong' error message. My tenant is in 'North Central US (Illinois)'.  It started with one workspace and then eventually all workspaces in the tenant integrated to Git are failing to sync.  Looking at the network calls in the browser dev tools, the Fabric UI git status response was a 400 after selecting the 'Sync branch' button.

I noticed the workspace/git/status API calls were failing and returned a 400 code. I tried to call git/status myself using the Fabric API and the error message said I needed to initialize the workspace. So I tried.

https://api.fabric.microsoft.com/v1/workspaces/<my workspace id>/git/initializeConnection

body payload

{
"initializationStrategy": "PreferRemote"
}

Here is the 400 response

{
  "requestId": "06c9683e-e02c-433d-8797-d6f6a9704708",
  "errorCode": "InvalidDefinitionFormat",
  "message": "Requested item definition format is invalid"
}

Maybe I do not have the correct body payload parameters. If I do, then Microsoft should fix this API call.

Same here, is there a working workarround for this, or we just need to wait and hopefully the functionality will be restored at some point with no time frame at the horizon?

For me it started to fail like this aprox 24 hours ago (at the moment I am writing this message). Also, in the developer console of the browser I have intercepted a message Invalid artifact definition format: LakehouseGit. In all the metadata and .platform files stored in GIT I don't have this type written. 

Also, what I observed is that, now, the Lakehosue and Warehouse created when a dataflow gen 2 is created, are no longer visible in the Source Control tab when there is a dataflow present in the workspace. Could these be related?