# PDFMonkey: Same Button, Two Clicks, Two Versions **URL:** \ **Category:** Ask for Help\ **Created:** [January 8, 2026, 4:13pm UTC](https://community.glideapps.com/t/pdfmonkey-same-button-two-clicks-two-versions/85931 "2026-01-08T16:13:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Yanis\_GACHOT](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/yanis_gachot/32/89366_2.png) [@Yanis\_GACHOT](https://community.glideapps.com/u/Yanis_GACHOT)\ **Post date:** [January 8, 2026, 4:13pm UTC](https://community.glideapps.com/t/pdfmonkey-same-button-two-clicks-two-versions/85931/1 "2026-01-08T16:13:10Z")
Hello everyone, I’m encountering a strange issue with PDF display in my Glide app using MonkeyPDF. Context: - I have completely replaced the old PDF with a new version in my database and in the editor. - In the development environment, everything is correct: on the first click of the button, the new PDF is generated and displayed. - On the user side, the behavior is different and reproducible: - On the first click, the button generates a PDF corresponding to the old version (which no longer exists in the database or in any components). - On the second click, the same button generates the new correct version. What we have already tested (user side): - Private/incognito browsing - Uninstalling and reinstalling the app - Testing on multiple browsers (including Chrome) and devices - Verifying that the old PDF is not referenced anywhere (tables, components, conditions) Despite all this, the old version still appears on the first click only for users. This behavior does not occur in my dev environment. Has anyone seen this kind of discrepancy (old version served on the first click, then new version on the second) with MonkeyPDF or Glide? Could there be a client-side or server-side mechanism that serves an old resource at the moment of the first generation? Any diagnostic ideas or suggestions would be greatly appreciated. Thanks in advance for your help. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [January 9, 2026, 1:26am UTC](https://community.glideapps.com/t/pdfmonkey-same-button-two-clicks-two-versions/85931/2 "2026-01-09T01:26:57Z")
> [@PDF Template ID Issue - Users Getting Old Template Despite Publishing Changes](https://community.glideapps.com/t/pdf-template-id-issue-users-getting-old-template-despite-publishing-changes/85745): > > 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 … That sounds like the situation here. I would submit a support ticket. ---
**Author:** ![Yanis\_GACHOT](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/yanis_gachot/32/89366_2.png) [@Yanis\_GACHOT](https://community.glideapps.com/u/Yanis_GACHOT)\ **Post date:** [January 9, 2026, 8:10am UTC](https://community.glideapps.com/t/pdfmonkey-same-button-two-clicks-two-versions/85931/3 "2026-01-09T08:10:14Z")
Yes, but this person is my coworker, and we’ve had this problem for a month without being able to resolve it. ---
**Author:** ![Lewis\_Parker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lewis_parker/32/91147_2.png) [@Lewis\_Parker](https://community.glideapps.com/u/Lewis_Parker)\ **Post date:** [January 9, 2026, 1:26pm UTC](https://community.glideapps.com/t/pdfmonkey-same-button-two-clicks-two-versions/85931/4 "2026-01-09T13:26:24Z")
Can you just use the pdfmonkey api instead, rather than the direct integration? cheaper on updates too if i remember correctly ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [January 10, 2026, 2:04am UTC](https://community.glideapps.com/t/pdfmonkey-same-button-two-clicks-two-versions/85931/5 "2026-01-10T02:04:36Z")
I use API almost exclusively these days, for the reason that I like to configure the body inside a JSON object/template compared to doing it in the action itself. I can also use that JSON object/template for other stuff in the app.