Fix Reconnect After Token Expiry
Diagnose reconnect after token expiry: separate OAuth, tier limits, sync credits, and PAUSED publish before touching bids.
Symptom reconnect after token expiry: check OAuth, customer ID, tier ceilings, then sync/Optimize credits.
- ✓Checklist for reconnect after token expiry: (1) OAuth scopes and correct customer ID, (2) Starter/Growth/Enterprise campaign or sync limits, (3) whether empty sync is a credit or tracking issue, (4) MCP PAT vs OAuth mismatch if using hosted MCP.
- ✓Fix the AdsDoneEasy path; do not invent auto-bid or live Meta workarounds.
- ✓Re-test after one change; avoid stacking MCP, OAuth, and bid edits.
- ✓Publish stays PAUSED; AdsDoneEasy does not auto-bid; Google bills media spend.
Why this matters
Layer isolate: fix-reconnect-after
Split auth, limits, sync, and publish when fixing reconnect after token expiry.
PAUSED vs failure
Confirm expected PAUSED behavior before treating reconnect after token expiry as broken live publish.
Credits check fix-reconnect-after
Verify sync/Optimize credits when diagnosing reconnect after token expiry.
Steps
Reproduce
Capture UI state and customer ID for reconnect after token expiry.
Check product constraints
Verify PAUSED publish, tier limits, and no-auto-bid expectations.
Apply one fix
Repair OAuth, credits, structure, or MCP auth for reconnect after token expiry.
Frequently asked questions
Is auto-bid included when running reconnect after token expiry?
Will reconnect after token expiry publish live campaigns automatically?
Is Google media spend inside the SaaS price for reconnect after token expiry?
What should I capture when reconnect after token expiry fails?
Related guides
Ready for profitable Google Ads?
Build verified Search campaigns and keep 100% control in your own Google Ads account.