InvalidAccessTokenError and expired Make.com connections

What changed outside the scenario

OAuth tokens expire, passwords change, admins revoke app access, and Google (or other providers) invalidate refresh tokens after idle time or security events. The scenario mapping can be perfect and still fail.

Make surfaces this as a connection / access error on the module that uses that connection.

What to check first

Open Connections in Make, find the connection named in the error, and reauthorize it. Confirm the account is the one the scenario should use.

If you recently edited the connection or rotated API keys, verify scopes still cover every module that uses it — a narrower key breaks modules that need write access.

After reconnecting, run once manually and confirm the same module that failed now succeeds before turning the schedule back on.

Do I need to rebuild the scenario?

Usually not. Fix or replace the connection, then re-test the failing module. Rebuild only if the app or module itself was deprecated.

Why does it keep expiring?

Some providers invalidate tokens on password change, after long inactivity, or when the same account is connected in many tools. Check the provider's security log and Make's connection scopes.