GATEWAY • OpenClaw quick fix

Gmail integration keeps disconnecting

If Gmail works once and then stops, the break is usually gateway health, expired credentials, or missing refresh/scope behavior.

In simple words: Make a safe copy if the step could change your setup, try the smallest check, then confirm OpenClaw is back to normal before doing more. The source link and commands stay below for people who want the technical detail.

Checklist

Check gateway status/health first (don’t debug the agent prompt if the gateway is down).

Verify credentials scope and refresh behavior (expired tokens look like flaky systems).

Add a tiny scheduled health ping so you learn about failures before you ‘need’ email.

Success looks like

• Gateway health check returns OK consistently.

• A Gmail test action succeeds without disconnecting on the next run.

Source: X post · link

Before the next risky OpenClaw change

Turn this quick fix into a repeatable rollback path.

If this touches tokens, providers, upgrades, plugins, or shared-agent settings, do the free check first — then use a verified snapshot and one restore drill before trusting unattended work again.

What openclaw.json Mastery adds

pre-change snapshot checklist
restore-drill steps before the real incident
gateway/config smoke test before agents run again

Use the free fix when: you only need to unblock this one low-risk change and can write the backup label, smoke result, and rollback trigger in your own notes.

Buy when: this same risk will happen again, another person needs to repeat the fix, or you want a purchase-to-first-GREEN receipt, restore drill, and written rollback record before agents run unattended.

Do not buy yet if: you have not tried the free checklist, you need live support, or you are not ready to make a verified backup before changing a working setup.

Use openclaw.json Mastery before the risky change →

Free fix first; buy the playbook only when the rollback path needs a repeatable first-GREEN proof record.

Have a high‑value nugget? Submit it.