On https://podcast.adobe.com/ - Enhance Speech V2 fails for multiple users – HTTP 423 Locked from phonons-server-flex.adobe.io
- 0 replies
- 22 views
- Translate
We are seeing a reproducible issue with Adobe Podcast Enhance Speech V2 affecting multiple users in our enterprise environment.
Affected service:
https://podcast.adobe.com/
Users are able to sign in successfully with their corporate Adobe accounts, and Adobe Podcast shows Premium access with available daily processing time.
The issue is specific to Enhance Speech V2.
When an audio file is uploaded and V2 is selected, processing fails immediately with:
"Enhance failed"
The same audio files process successfully when using Enhance Speech V1.
We have reproduced the issue across multiple users and on both Windows and macOS systems.
Troubleshooting completed:
-
Tested multiple user accounts
-
Tested on Windows and macOS
-
Tested multiple audio files and file lengths, including an approximately 11-second test file
-
Tested WAV and M4A files
-
Signed out and back into Adobe
-
Cleared Chrome browser cache
-
Tested Chrome Incognito
-
Confirmed Premium access
-
Confirmed daily processing allowance remains available
-
Confirmed the same files successfully process using Enhance Speech V1
During reproduction, Chrome Developer Tools shows the Enhance Speech V2 request failing with:
POST https://phonons-server-flex.adobe.io/api/v1/enhance-speech/tasks
net::ERR_ABORTED 423 (Locked)
This suggests the V2 request is reaching the Adobe backend but is being rejected before the enhancement task is processed.
The issue has also been reproduced by our Broadcast Engineering Team Lead using a separate account.
Adobe Enterprise Support case E-002553425 was opened, but Enterprise Support advised that Adobe Podcast is not currently supported through that channel and directed us to this Community page.
Screenshots are available showing:
-
The Adobe Podcast "Enhance failed" message
-
Chrome Developer Tools showing the HTTP 423 (Locked) response
Has anyone else seen HTTP 423 (Locked) specifically with Enhance Speech V2, or can Adobe confirm whether this indicates a backend service, entitlement, provisioning, or account-related issue?
Any guidance on additional logs or diagnostics that would help isolate the V2 failure would be appreciated.
