I am using Workers in Workflows and I am running up against the 1000 subrequests limit. my question
I am using Workers in Workflows and I am running up against the 1000 subrequests limit. my question is is there a way to clearly see what are the subrequests made in a Worker?
so for context, my worker is trying to do long running job in batches. the issue is I am using another Durable Object as a rate limiter. the problem with rate limiting is I can’t estimate how frequently the rate limiter will be called in a single worker run.
now that I’ve gotten rid of the rate limiter, it seems to not run into the subrequest issue anymore.
my feedback would be:
so for context, my worker is trying to do long running job in batches. the issue is I am using another Durable Object as a rate limiter. the problem with rate limiting is I can’t estimate how frequently the rate limiter will be called in a single worker run.
now that I’ve gotten rid of the rate limiter, it seems to not run into the subrequest issue anymore.
my feedback would be:
- if a Worker in a Workflow has hit the subrequest limit, it seems pointless to retry since any retries would also by definition hit the same limit
- I personally feel that this subrequest limit really dampens the promise of Cloudflare platform being serverless and scales infinitely, esp if it includes calling internal Cloudflare resources like Durable


