PDF Template ID Issue - Users Getting Old Template Despite Publishing Changes

Ask for Help
,
1

Description:

I’m experiencing a persistent issue where some users in the live environment are generating PDFs with an old template ID, while the development environment works correctly with the updated template ID.

Steps Already Taken:

  • Verified auto-publishing is enabled and manually published changes multiple times
  • Had affected users clear app cache, force-quit and reopen the app
  • Tested switching to affected user accounts in builder (works correctly there)
  • Confirmed the same template ID is used in both development and live environments

Issue Details:

  • When I test as the affected user in the builder, PDF generation works with the correct template ID
  • In the live environment, the same user gets PDFs generated with the previous template ID
  • This suggests user-specific caching that standard cache clearing hasn’t resolved

Request: Please help resolve this persistent template ID caching issue that affects specific users in the live environment.

2

Can you detail how users are generating the PDFs? Is it through some sort of HTML to PDF conversion? If so, how is that HTML being generated? Or is the PDF being generated through one of the Glide integrations?

1 Like
3

Actually, I’m using a Glide integration with PDFMonkey. Users only need to click a button that triggers the workflow to generate the PDF. However, they are still receiving a PDF generated from the previous template, without the updates, even though the template ID in the Builder and the one in Live are the same.