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.