Custom Libraries random auto deletion when publishing

[LFdz11]

Hi. 
I'm facing the same recurrent issue when updating custom libraries in an environment. Let's say I have 3 (A, B, C) custom libraries in the env, I have updates to publish in A and C, so I loaded them and publish, but randonmly library B gets deleted, so once the publish has finished, and I tried to use all 3 libraries and B is no longer in env. Initially I solved it republishing all of them together regardless of if they were changed or not, but now even that is not working. What is the right way to make it work? I have tried deleting and republishing, not working. Same happens with the github integration library is detected as deleted in github. 

[v-prasare]

Hi @LFdz11,

We would like to follow up to see if the solution provided by the super users resolved your issue. Please let us know if you need any further assistance.

@burakkaragoz, thanks for your prompt response.

Thanks,

Prashanth Are

MS Fabric community support.

If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

[burakkaragoz]

Hi @LFdz11 ,

Just checking in. Did the previous suggestions help resolve your issue?
✅ If it’s working now, feel free to mark the response as the Accepted Solution. This helps others who face the same issue find the fix faster.
✨ And of course, a little Kudos would be much appreciated!
If you're still running into trouble, let me know what you've tried so far and I’ll help you dig deeper. We’ll get it sorted!

[burakkaragoz]

Hi @LFdz11 ,

Yeah, I've seen this kind of issue before, it's really frustrating when libraries kinda disappear after publishing. From what you described, sounds like the environment's deployment process is not handling the custom libraries' state consistently, especially when not all are changed.

A couple of things to double check:

• When publishing, are you sure all libraries are properly referenced in your environment configs or deployment script? Sometimes, if a library isn't listed or loaded, the platform might just think it should be removed.
• If you use any automation (like CI/CD integration), make sure the scripts always include all existing libraries, not just the changed ones. Otherwise, the system may assume missing ones should be deleted.
• You already tried deleting and republishing but did you try exporting the current state of the environment first, then comparing it to what you’re about to publish? Sometimes there are small mismatches that cause this.
• For the GitHub integration, make sure your repo and the environment are fully in sync before publishing. If the library is missing from the repo, the system might flag it as deleted.

If nothing helps, you might want to open a support ticket with more details and maybe include logs or exact steps. This really looks like a bug in how the environment tracks libraries between publishes.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.