#gog auth keeps expiring every few weeks making email send crons unreliable.

1 messages · Page 1 of 1 (latest)

pallid mango
#

Every several weeks my crons that rely on agents sending emails fail because of an expired gog auth from gmail. so crons that send emails fail. why is authentication needing to be redone so frequently? any workarounds or better agent email solutions?

royal scaffoldBOT
devout baneBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

royal scaffoldBOT
sturdy juniperBOT
#

Let me check the actual docs path and the auth behavior in source so I don’t make this up.

#

I’m checking whether OpenClaw has a more reliable built-in alternative than Gmail OAuth before I recommend one.

#

This is usually Google, not OpenClaw.

Most likely cause: your Google OAuth app is External + Testing. Google says refresh tokens in that setup can expire after 7 days for Gmail scopes, which is exactly what gog uses.

Other official Google causes:

  • account password changed
  • too many live refresh tokens for the same user/client
  • token was revoked
  • token went unused for 6 months
  • Workspace admin policy / time-based access

Also, if you run OpenClaw in Docker/VM, make sure the Gmail keyring is actually persistent and GOG_KEYRING_PASSWORD stays stable, otherwise the auth can look “lost” after restarts. Docs: https://docs.openclaw.ai/install/docker-vm-runtime

What I’d do:

  1. Paste openclaw --version
  2. Check Google Cloud → OAuth consent screen → is it Testing or Production?
  3. If containerized, confirm ~/.openclaw is persisted and GOG_KEYRING_PASSWORD is not changing