Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@kptdobe
Copy link
Contributor

@kptdobe kptdobe commented Dec 16, 2025

In the logs, we can observe a frequent warning for POST requests on /source (1.7k entries in the last 7 days):

A stalled HTTP response was canceled to prevent deadlock. This can happen when a Worker calls fetch() or cache.match() several times without reading the bodies of the returned Response objects. There is a limit on the number of concurrent HTTP requests that can be in-flight at one time. Normally, additional requests made beyond that limit are delayed until previous responses complete. However, because the Worker did not read the responses, they would never complete. Therefore, to prevent deadlock, the oldest response was canceled. To avoid this warning, make sure to either read the body of every HTTP Response or call response.body.cancel() to cancel a response that you don't plan to read from.

Just warnings from the worker, no error.

@kptdobe kptdobe requested a review from tripodsan December 16, 2025 08:54
@kptdobe kptdobe merged commit d32fa3e into main Dec 17, 2025
6 checks passed
@kptdobe kptdobe deleted the stalled branch December 17, 2025 14:29
adobe-bot pushed a commit that referenced this pull request Dec 17, 2025
## [1.0.3](v1.0.2...v1.0.3) (2025-12-17)

### Bug Fixes

* stalled response ([#226](#226)) ([d32fa3e](d32fa3e))
@adobe-bot
Copy link
Collaborator

🎉 This PR is included in version 1.0.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants