Hi @Susana_Cardenas,
I think this issue often relates to either overwritten policies or improper filter.xml configurations during deployment.
When deploying new content packages (especially editable templates and policies), the filter.xml
configuration plays a critical role in determining what gets overwritten, merged, or deleted in the JCR repository.
If your deployment package includes template or policy paths without care, you may be overwriting or deleting existing policies, leading to:
Make sure your filter.xml
has proper mode or excludes cq:policy
paths if you don't intend to overwrite them.
Bad example (might overwrite policies):
Be more specific with includes:
<filter root="/conf/your-site/settings/wcm">
<include pattern="/conf/your-site/settings/wcm/templates(/.*)?"/>
<!-- Do not include policies if you don't want to overwrite -->
</filter>
Include your policy definitions under in your codebase, typically under ui.content
or a dedicated content package, and deploy them along with your templates and editable components - instead reconfiguring manually after each build.
Santosh Sai

