AEM FORMS Custom fonts are disappearing after 2-3 days in AEMaaCS

[satish_puli]

Hello Community Experts,

We are working on a migration project from AEM 6.5 to AEMaaCS. We have large number of XDP templates with custom fonts to migrate. We have followed this article https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/forms/using-comm... from adobe to add custom forms to the project repository and deployed to cloud. When we generate Pdfs, Fonts are working fine during the initial 2-3 days and after that custom fonts are missing in the pdf generated out of xdps. Once I redeploy the code to cloud again fonts are working as expected. Same issue is occuring every 2-3 days. Can you please suggest how to fix this issue?

[tripti_singh]

Hi @satish_puli 
From what you’re seeing,it seems that the custom fonts are not reaching all document Services pods.

Possibly:
- The fonts might not be packaged as a proper font archive, so some pods don’t pick them up after they restart or rotate.
-Or only a few pods have the fonts, which makes the problem feel random depending on which pod handles the request.

For starters, could you please check below:
- Make sure your custom fonts are in their own Maven module with the correct font-archive headers. This is what tells Cloud Manager to deploy them properly. (as mentioned in document)
-Double-check that this module is listed in your parent `pom.xml, otherwise it won’t consistently build or deploy.
-Ensure your Cloud Manager pipeline builds and deploys the fonts module every time. That way, any new pod that comes up always has the fonts.
-Notice when the issue starts: if it happens right after a deployment or pod rotation, it’s a strong sign the fonts aren’t being picked up by all pods.
-Verify your XDP templates only reference fonts included in your font archive/custom font or the default system fonts as well.

Also, confirm on the current version you are on.