Skip to content

fix(github): reduce merged GraphQL batch size to avoid resource limits #3559

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
setchy merged 1 commit into from
Oct 29, 2026
Merged

fix(github): reduce merged GraphQL batch size to avoid resource limits #3559

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions src/renderer/utils/forges/github/enrich.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down
Loading