How to know when subrequest limit is hit?
We have some long-lived (always on) websockets terminating on our worker, and it appears we lose communication to the outside world after some time. We were initially making HTTP calls out during the request. We've since moved that sending messages to a queue, and handling these with another worker. No change in behaviour though.
I suspect we're coming across subrequest limits. And it looks like calls to internal services are limited too (albeit with a higher limit).
How would I able to confirm that the subrequest limit was hit for a particular request? Is there a way to detect this while the worker is running?
1 Reply
Sub request limits appear in the form of an exception thrown by the fetch/binding call - there isn’t any other way to track how close you are to that limit, until you hit it