Auth, Rate Limits, and API Quotas
Most recurring failures come from token lifecycle issues or backend throttling behavior.
Fast Diagnosis Table
| Signal | Likely cause | Immediate action |
|---|---|---|
| 401 Unauthorized | Expired/invalid token | Reconnect remote auth |
| 403 Forbidden | Missing permission | Review IAM or app scope |
| 429 Too Many Requests | Rate limited | Reduce concurrency, set --tpslimit |
Stabilization Command Pattern
stabilize-api-load.sh
rclone sync /srv/data remote-prod:backup/data \
--transfers 6 \
--checkers 12 \
--tpslimit 8 \
--retries 10 \
--retries-sleep 15s
Auth Recovery Commands
rclone config reconnect remote-prod:
rclone lsd remote-prod:
note
If auth succeeds manually but fails in scheduler, verify job user and config path are identical to manual test context.