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 property-management robot's AI key is being rejected, so it can't log into AppFolio for Western Slope right now (and will hit the same wall for every other customer once their sessions go cold too) — rotate the key, or hold off and dig deeper first?
The full question, as raised
appfolio-browser-agent's prod ANTHROPIC_API_KEY (Vercel, set ~174d ago, last touched commit 341fc42 2026-09-09) is being rejected by Anthropic with a 401 (AI_APICallError: invalid x-api-key) inside Stagehand's login drive. No code/dep change landed near the first failure (19:26Z) or the deploy right before it (f84df55, 14:42Z) — ruling out a regression. 2 failures in 24h tripped the identity breaker's escalated 6h lockout for westernslopepm (identity=7304169e) at 19:58Z; downstream callers (issue JAVASCRIPT-NEXTJS-Y3, fetch-lease-pdf) are being refused live, 3 events in the last hour alone. The breaker self-clears ~01:58Z and will immediately re-trip on the same dead key, re-locking for another 6h, then repeat — this will not self-heal without a credential fix.
Why, and what was tried
The session raising this recommends: Rotate the key now it's a 401, not a transient 5xx/rate-limit, and it's already causing live customer-facing refusals (lease-PDF fetches) with no sign of self-recovery Tried first, unsuccessfully: Confirmed no code/dependency change near the failure (git log on stagehandFactory.ts and package.json, both last touched 2026-09-09); confirmed the key has been 'set' 174 days per vercel env ls; confirmed only 2 occurrences ever of this exact error in Sentry, both within the same 32min window; confirmed live downstream impact via Y3's event timestamps after the trip. Did not rotate the key myself — that's a secrets/credentials hard-stop, Fede's call.