You may see NoSuchKey or The specified key does not exist if you’re using async mode and try to access the output before the job is finished processing.
How to fix it
Add a background job check to your code to wait until the job is marked as complete before accessing the output.
We provide ready-made code samples for managing background jobs here: Background Job Handling
Using Postman?
If you’ve set async: true, the API will return a jobId.
Use the /job/check endpoint to check the job status using this jobId.
Find the Background Job Check in our Postman Collection here: Postman Collection Docs
Using Zapier?
If you're using Zapier, please provide us with the following so we can review it:
Your PDF.co email address
The Job ID (if available)
Using Make or Similar Automation Tool?
Automation platforms like Make have timeout limits (30 seconds–5 minutes). To handle long-running jobs:
Add a delay step in your workflow
Then check the status again after the delay using the Background Job Check module
This helps avoid premature access or timeout errors when processing large files.