From d33240c899191d416cc95418359b1530d375ee4f Mon Sep 17 00:00:00 2001 From: Adam Setch Date: Wed, 28 Oct 2026 22:11:39 -0400 Subject: [PATCH] fix(github): reduce merged GraphQL batch size to avoid resource limits --- src/renderer/utils/forges/github/enrich.ts | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/renderer/utils/forges/github/enrich.ts b/src/renderer/utils/forges/github/enrich.ts index 27be14e2d..6f7a76ee1 100644 --- a/src/renderer/utils/forges/github/enrich.ts +++ b/src/renderer/utils/forges/github/enrich.ts @@ -7,11 +7,12 @@ import { createNotificationHandler } from './handlers'; /** * Maximum number of notifications batched into a single merged GraphQL query - * by `enrichGitHubNotifications`. GitHub's GraphQL alias cap is well above - * 100; this is a conservative ceiling that keeps individual responses small - * and parseable. + * by `enrichGitHubNotifications`. Each aliased fragment pulls nested + * connections (labels, comments, replies), so larger batches (50+) trip + * GitHub's "Resource limits for this query exceeded" error and fail the + * whole batch. */ -export const GITHUB_API_MERGE_BATCH_SIZE = 100; +export const GITHUB_API_MERGE_BATCH_SIZE = 25; /** * Enrich GitHub notifications with additional subject details (state, user,