Generic SdkException on some PDFs is a timeout - set custom ClientConfig timeouts

TL;DR

10s connect and 40s read - and pass it into the ExecutionContext alongside your credentials.

Steps

1. When the SDK throws the generic Request could not be completed error on specific PDFs, suspect the default timeouts before the documents. Build a ClientConfig with explicit timeouts - e.g. 10s connect and 40s read - and pass it into the ExecutionContext alongside your credentials. The reporter's files parsed fine once the read timeout was raised; the SDK just gave up too early and wrapped it in a meaningless exception.

When to use

You are seeing this: When the SDK throws the generic Request could not be completed error on specific PDFs, suspect the default timeouts before the documents. Use this skill when you run into "Generic SdkException on some PDFs is a timeout - set custom ClientConfig timeouts".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow 68372461 (accepted answer, 2 votes): Adobe PDF Services threw a generic SdkException - Request could not be completed - on some company report PDFs with no useful detail. The accepted answer found the files were fine in Node and diagnosed it as a timeout, not a document problem.

Verified resolution: When the SDK throws the generic Request could not be completed error on specific PDFs, suspect the default timeouts before the documents. Build a ClientConfig with explicit timeouts - e.g. 10s connect and 40s read - and pass it into the ExecutionContext alongside your credentials. The reporter's files parsed fine once the read timeout was raised; the SDK just gave up too early and wrapped it in a meaningless exception.

Source URL: https://stackoverflow.com/questions/68372461