PDFMonkey: Same Button, Two Clicks, Two Versions

Ask for Help
1

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.

1 Like
2

That sounds like the situation here.

I would submit a support ticket.

1 Like
3

Yes, but this person is my coworker, and we’ve had this problem for a month without being able to resolve it.

4

Can you just use the pdfmonkey api instead, rather than the direct integration? cheaper on updates too if i remember correctly

1 Like
5

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.

1 Like