I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. The background Claude lane that writes tenant summaries and tags conversations only has 2 subscription logins, and both keep getting rate-limited — want to add more logins to that pool, or leave it as is?

The full question, as raised

backgroundClient()/buildBackgroundClient() in propflowai reads ANTHROPIC_BACKGROUND_AUTH_TOKEN as a comma-separated bearer pool; prod currently has exactly 2 entries. Sentry shows this pool fully exhausting repeatedly over the last 3 days across multiple background lanes: tenant-summary generation (JAVASCRIPT-NEXTJS-1JS/1JR/1J4, 'all 2 subscription tokens refused: 2 rate-limited') and conversation topic-stamping (JAVASCRIPT-NEXTJS-1J8, 20 occurrences since 2026-10-17, 'retries exhausted'). Each account has a hard weekly cap with ~21h lockout once blown, so 2 accounts give very little headroom once background traffic grows. The failure mode is already handled gracefully in code (empty/stale summary with an 'unavailable' flag; a message just goes untagged) — nothing crashes or 500s — but the feature silently degrades for users during the lockout window, and the pattern is getting more frequent, not less, since the 2026-10-04 change that moved background traffic back onto the subscription pool.

Add a couple more spare logins to that poolthe raiser's pick Leave it at two logins for now I'm not sure — go find out Take it to the engineering bridge

Why, and what was tried

The session raising this recommends: Add a couple more spare logins to that pool
the pool is now shared by at least two user-visible features and failures are trending up (20x in 3 days on one lane alone); adding accounts is cheap and reversible, unlike eating recurring degraded UX
Tried first, unsuccessfully: checked for an open decision on this exact cause first (blocked outstanding) — found none; the closest prior decision (b89479387, Sep 15) was Gera choosing to leave a DIFFERENT job (the website-specials scraper) on the shared login rather than provision it a dedicated key, which doesn't cover this broader, growing pool-exhaustion pattern

972a3685 is parked on this.

Pick an option above, then press Done.