@feld @i @olivia The exact error might be irrelevant since they might also have some geoblocks or other :cloudflare: shenanigans going. What's more concerning is pileup happening in a first place; now that I'm thinking about it might be recursion.
1. pleromer receives an activity referencing that guy's profile/post
2. it fetches them
3. fetch pipeline kicks in
4. pinned posts fetching happens as a part of pipeline
5. pleromer inserts RemoteFetcherWorker jobs for those posts
6. said jobs try to fetch pinned posts again
If that's the case (too lazy to confirm, sorry) and fetcher jobs start erroring out, the queue raises exponentially. Hopefully not?