All 1Password CLI (op) calls suddenly fail with rate-limit errors. This affects
both Hermes tools and ExternalSecrets Operator (ESO) in K8s simultaneously.
The outage lasts approximately 1 hour.
Root Cause
The 1Password CLI enforces rate limits at the account level, not per-token or
per-client. When ESO polls aggressively (multiple SecretStores + frequent sync intervals),
it exhausts the quota for the ENTIRE account, blocking all other op callers including
Hermes automation.
Mitigation
Stop ESO immediately — scale down the ESO deployment to halt API calls:
Wait 1 hour — the rate limit resets automatically. No polling needed.
Resume ESO with reduced polling frequency afterward
Prevention
Reduce ESO refreshInterval to 10+ minutes (not the default 1 minute)
Limit the number of SecretStores that reference 1Password
Consider caching secrets locally to reduce API pressure
Never run op in tight loops — always add delays for batch operations
Nie op read pro Watchdog-Tick: statische Secrets (HA-Long-Lived-Token, API-Keys) in einen lokalen 0600-Cache legen, op nur on-miss/401. Ein 15-Minuten-Watchdog macht sonst 96 Reads/Tag und wird bei jedem Limit blind (2026-11-06: free@home-Watchdog meldete „BLIND (RuntimeError)").
Bei anhaltendem Limit (>10 min ohne lokalen Verursacher) zuerst ESO prüfen:kubectl logs -n external-secrets deploy/external-secrets --since=10m | grep -c "rate limit exceeded". Fehlschlagende ExternalSecrets mit kurzem refreshInterval erzeugen einen Retry-Sturm, der die Quote dauerhaft verbraucht.
5 ES mit refreshInterval: 1h (authelia-oidc-jwks/-secrets, postgres-main-db, paperless-ai-secret/-oidc-secret) sind die üblichen Verdächtigen — Rest steht auf 12h.
Evidence
Hit twice: Jul 2026 (initial discovery) and during token corruption investigation