Fabric GIT integration error - Workload Error Code Git_InvalidResponseFromWorkload

[avt]

I have 2 Fabric workspaces, Development WS connected to a develop (default ) branch and Prod WS connected to main (created on develop) branch in Azure Git.

When I synced my Devleopment workspace with Develop branch (default) which had Pipeline and Lakehouse additions, it worked seemlesly.

However when merge these updates from develop into main and sync my Prod workspace with my main branch, syncing fails on pipleline and lakehouse with this error message:

Cluster URI https://df-msit-scus-redirect.analysis.windows.net/ 

Request ID 0c58f07c-fc61-326e-1411-d7f9629cdfa3

Workload Error Code Git_InvalidResponseFromWorkload

Time Tue Jan 02 2024 07:00:23 GMT-0800 (Pacific Standard Time)

Has anyone seen this behavior and how to resolve this?

[dnope]

Hi, same problem here. I have "Something went wrong. Please check the technical details for more information. If you contact support, please provide these details.
Details : Workload Error Code Git_InvalidResponseFromWorkload"

This only happens with Lakehouse.

[CarlosSerna]

This issue happens when you have deactivated activities inside a pipeline.
To solve this issue you need to reactivate the deactivated activities in pipelines or delete them.

[avt]

Hi @Anonymous , thnaks for responding. I am the only person working on this right now. And I was moving it from Dev to Prod (default branch to main branch ) soon after i completed merging into default brnach. So no changes were made. Here are my steps:

1. created lakehouse and data pipeline in my local WS

2. merged the changes from local WS branch into develop branch (default)

3. synced my Development WS connected to develop branch. All changes got synced with no errors. 

4. created cherrypick branch and merged that into main branch.

5. synced my Prod WS connected to main branch. I get this error for pipeline.

Now when I test this for only Lakehouse, following steps 1 through 5, same error but on Lakehouse.

I am beginning to think this is some sort of dependency bug in the product because only it throws this error only non-pbip files. pbip files works with no issues. 

I have raised a ticket with support team and waiting to hear back from them.

If you have more thoughts on the error and how it could be fixed, please let me know.

Thank you!

AV 

[Anonymous]

HI @avt,

According to the error message, it could be caused by the conflict that has occurred when changes are made to the same item in both the workspace and the remote Git repository.

In my opinion, I think you should fix the conflict on Git at first. 

For conflicted item, you can choose to accept the incoming changes from the Git repository or keep the current version that’s in the workspace.

Also, you can revert either the entire workspace or Git branch to last synced state. (if you revert the Git branch to a previous commit, you can still see the changes made to the unsynced branch)

If you’re not sure what changes were made and which version to choose and don’t want to revert to a previous state, you can try resolving the conflict in the Git repo by creating a new branch, resolving the conflict in that branch, and syncing it with the current one.(Note that only a workspace admin can reconnect the workspace to the new branch)

Regards,

Xiaoxin Sheng