Failed to poll docs for Liplus-Project/dipper_ai: Too many subrequests by single Worker invocation
Failed to poll releases for Liplus-Project/dipper_ai: Too many subrequests by single Worker invocation
Failed to poll Liplus-Project/dipper_ai: Too many subrequests by single Worker invocation
Failed to poll docs for Liplus-Project/liplus-language: Too many subrequests by single Worker invocation
Failed to poll releases for Liplus-Project/liplus-language: Too many subrequests by single Worker invocation
Failed to poll Liplus-Project/liplus-desktop: Too many subrequests by single Worker invocation
... (5 リポ × 3 surface 程度の組み合わせで 90 件)
observation
2026-05-07 10:48 JST、Cloudflare Workers Observability で
Too many subrequestsを直近 24h 範囲で観測したところ 90 errors ヒット。集中時刻は May 7 00:01 JST の 1 周。pollComments側 (#134, cap=30→10 by PR #144) は同日 :15 cron でfetch budget reached (10 fetches)warn のみ・errors 0 で安定確認済み。本件は別 surface (pollDocs/pollReleases/ 統合 poller) で同 root cause が独立に発生している。hypothesis
Cloudflare Workers の 1 invocation あたり 1000 subrequest 制限を、
pollDocs/pollReleasesを含む重い cron 周回で超過している。pollComments(#134) と同じ root cause pattern。集中時刻が May 7 00:01 JST 1 周のみであるところから、daily 系または hourly :00 cron で per-repo fan-out (docs + releases + 親 poll) × 5 リポ × 1 fetch あたりの overhead (Vectorize embed / D1 upsert / Workers AI) を掛け合わせて 1000 を割っていると推定。fix direction (memo)
pollComments(bug(poller): pollComments exhausts Worker subrequest budget on dipper_ai #134, PR fix(poller): lower pollComments cap from 30 to 10 to fit Worker subrequest budget #144) と同形のパターン適用：MAX_DOCS_FETCHES_PER_REPO_PER_RUN/MAX_RELEASES_FETCHES_PER_REPO_PER_RUN系の per-repo cap をsrc/poller.tsに導入。残り parent は次回 cron に持ち越し。related
pollCommentsside, resolved)