Custom Libraries random auto deletion when publishing

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.