Status: Needs Follow-up
Priority: High (recurring blocker, automation down)
Today's daily negatives tune-up could not run. Every OAuth-based backend that talks to the Google Ads API is blocked by the same root cause: our OAuth refresh token has expired again. Zero search-term data was pulled, so no adds, no removals, no campaign changes were made. Budgets and bids untouched.
The permanent fix was already flagged in a prior session memory: the OAuth consent screen for the Google Cloud project that owns our Ads API client is stuck in Testing mode, forcing refresh tokens to expire every 7 days. Moving it to In production (or switching User type to Internal on a Workspace org) stops the weekly expiry cycle.
Tried two different refresh tokens:
.env token at C:\Users\SAguiar\Documents\Projects\_repo-staging\claude-ads\.env → invalid_grant: Token has been expired or revoked.Per skill spec, invalid_grant is not retried in a loop.
Repo present locally but it uses the same OAuth client ID and consent screen as Backend 1. Same root cause would apply. Not re-executed.
Not connected in this scheduled session. Connecting a new MCP requires interactive user approval (unavailable in an automated run).
Tool prefix not present in the current session's tool list.
Per Sam's direction ("try the other oauth app (lunar-arc...)"), I attempted to use the SAIL-named OAuth client from the lunar-arc-493119-a6 Google Cloud Project. Result: also blocked.
961786446236-gv0hctl8qbctat7knd381uigs1cuf0jl.apps.googleusercontent.com