Skip to main content
Participant
September 18, 2026
Question

BUG: PDF Services API — Set Form Data Jobs Stuck "In Progress" Since September 17

  • September 18, 2026
  • 2 replies
  • 16 views

PDF Services API — Set Form Data Jobs Remain "In Progress"

We have an application that has been successfully using the Adobe PDF Services REST API to populate PDF form fields. It was working normally until September 17, 2026.

Our application successfully authenticates, creates the asset, uploads the PDF, and submits the Set Form Data operation. Adobe accepts the job and returns the job Location as expected.

However, when we poll the job Location, Adobe continuously returns:

{"status":"in progress"}

The job never reaches "done" or "failed." Our application currently stops polling after 180 seconds.

We reproduced this problem three times on September 17 using the same PDF/form workflow that previously worked successfully.

We have verified the following in our Adobe Developer account:

• PDF Services API is active.
• OAuth Server-to-Server credentials are active.
• Usage is only 11 of 500 document transactions for September.
• Adobe Developer Console shows service activity on September 17.

We have also been seeing this error repeatedly in Adobe Developer Console:

Service getProjectById failed.
Error code: 500
Error message: Cannot read properties of undefined (reading 'status')

Is there currently an incident affecting PDF Services API, specifically Import PDF Form Data / Set Form Data jobs?

Could this be related to the broader Adobe service incident being investigated beginning September 17?

The important distinction in our case is that Adobe accepts the Set Form Data request successfully, but the asynchronous job remains "in progress" and never completes.

Thank you.

2 replies

Participant
September 18, 2026

There was an issue that just got solved: https://status.adobe.com/products/503500
I recommend you to check status page when you again meet such issue to be up to date

Participant
September 19, 2026

This fixed the issue.  Thank you.