Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
thecatfix
1 month agoDedicated Contributor
Service Account Rate Limits: 15+ Minutes Block, No Backoff Duration Shown
Environment: - 1Password CLI (latest) - Service Account (not personal account) - Linux systemd service using LoadCredentialEncrypted - op inject to load 2 secrets at startup --- The Problem ...
thecatfix
1 month agoDedicated Contributor
1Password rate‑limiting is the kind of "enterprise security feature" that makes you want to take your laptop, walk into the sea, and let the tide solve your problems
You buy the secrets management control plane (the thing that's supposed to be the adult supervision for autonomous agents) and it turns into a bouncer at your own front door going:
"Whoa, whoa, mate, too many requests… come back later."
Congratulations -- your "secure mediation layer" just turned into a chaos generator that makes your agent look incompetent and your infrastructure tool
The one job is: **be boring under pressure**.Not "be a surprise traffic cop when the user is already dealing with rate limits somewhere else."
When you rate-limit the credential plane, you're not protecting me -- you're stranding me mid‑operation with a half‑built robot and a pile of broken glass.
Rate limits are fine. But if you're going to throttle, at least
- give a real retry-after
- make failures explicit and atomic
- don't turn normal automation into an improv comedy about authorization headers.
Right now it's less "security" and more "a seatbelt that randomly punches you in the throat.
Look at what Doppler offers
Action Doppler 1Password
Read Requests 240 to 480 per minute 1,000 per hour
Write Requests 60 to 120 per minute 100 per hour
Daily Hard Cap None (Usage-based) 1,000 requests per 24 hoursScopePer Project/EnvironmentPer 1Password Account