PDF.co link expiration issue

Features
1

Out of the blue, a PDF.co module (“Split PDF”) in one of our critical scenarios is failing, and after some investigation it seems the various server times are asynchronous, so the output file that the PDF app is creating in AWS bucket has an expiry time which precedes the request time.
We upgraded our PDF.co subscription (Business 2 plan with 1440-min expiration support), and increased the Output Links expiration to 720 minutes (instead of 60) which our new plan supports.
I regenerated a new API key, and created a new connection for this node.
However the native PDF-dot-co modules in Make still return a 400 error when we set expiration > 60 mins. This is the error message:
“Error
400 Failed to validate the Job: The ‘expiration’ parameter must be less than or equal to 60 minutes.”

At present the scenario is stuck and cannot run, causing complications in our workflow.

I’ve submitted a ticket to Support, but in the meantime has anyone experienced this or have any suggestions? This issue literally arose out of the blue after running smoothly for well over a year.

3

Issue resolved. Recording here in case any community members experience the same problem.

I contacted PDF.co support who identified that a recent update to their PDF Split endpoint caused the problem we experienced. As an immediate fix, they switched our account back to the previous stable version of the endpoint.

The scenario is now working as previously. Just a note as well that finding the problem was being caused by asynchronous server times was like finding a needle in a haystack, so if you’re getting a 403 error without much detail, it’s worth looking at the file creation and expiration logs to check the timestamps.

2 Likes
4

Hello @Koin_Admin :waving_hand:

I just wanted to take a moment to appreciate you coming back and sharing the solution. I believe it will help other Makers in need. :hugs: Thank you!