# \[Bug\]: Known GitHub quota pauses repeatedly log full warning stacks in thread PR discovery and settlement · Issue \#19781 · pingdotgg/t3code [View on GitCafe](https://git.cafe/pingdotgg/t3code/issues/19781) Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code) Visibility: public State: backlog Priority: 0 ## Description [Discussion and activity](https://git.cafe/pingdotgg/t3code/issues/19781) --- ### Before submitting - [x] Searched quota-pause, settlement and PR-discovery reports. - [x] Included log counts, scope limits and the catch paths. ### Area apps/server ### Steps to reproduce 1. Have unresolved branch PR lookups in threads eligible for PR discovery or automatic settlement. 2. Let the GitHub account enter a `SourceControlRateLimitPausedError` pause until its known reset time. This can be caused by other tools sharing the token; T3 need not exhaust the quota itself. 3. Allow the periodic sweeps to run during that pause. ### Expected behavior An expected, already-known quota pause is summarized or throttled until `retryAt`, while unexpected failures retain useful warning stacks. Repeated blocked groups should not emit the same full stack every sweep. ### Actual behavior and evidence [`ThreadPullRequestService.synchronize`](https://github.com/pingdotgg/t3code/blob/e536bfd33bc3c351997141d93790df75eeded7b9/apps/server/src/orchestration-v2/ThreadPullRequestService.ts#L346) logs `thread branch pull request lookup failed` with all grouped thread IDs and `Cause.pretty(cause)`. [`ThreadSettlementService.sweep`](https://github.com/pingdotgg/t3code/blob/e536bfd33bc3c351997141d93790df75eeded7b9/apps/server/src/orchestration-v2/ThreadSettlementService.ts#L537) does the same with `automatic thread settlement skipped`. Neither catch path treats the known quota-pause reason specially. The sync reactor already has quota-pause/backoff handling (#16203); these sibling paths still warn per group on later sweeps. Read-only recount of the retained Linux service log (approximately 17 days) separated actual quota-paused records from other errors: | Warning | Records containing `SourceControlRateLimitPausedError` | Bytes of those records | | --- | ---: | ---: | | thread branch pull request lookup failed | 68 | 179,040 | | automatic thread settlement skipped | 68 | 177,366 | | Total | **136** | **356,406** | The whole log was 1,179,312 bytes, so these expected-pause records alone were **30.2%**. Both prefixes including unrelated failures totaled 447,866 bytes; that larger total is **not** all quota-pause noise. These were multiline warning records, split at timestamped log headers, rather than a count of matching individual lines. ### Impact / version / environment Minor diagnostic noise. The entire retained service log is only about 1.18 MB; this report does not claim a disk-capacity problem, high CPU, a GitHub network retry storm, or that T3 exhausted the token. Quota admission already refuses the paused reads correctly. The defect is repeated warning-level stack output for an expected condition. Ubuntu Linux service, historical nightly logs through `0.0.46-nightly.20261014.3132`; both catch paths still present on `main` `e536bfd33bc3c351997141d93790df75eeded7b9`.