An integration stopped working

Summary#

An integration that worked yesterday can stop working today for one reason: the permission you granted is no longer valid. Metric Vault never silently drops a connection, so when a Google or social channel goes quiet, the access was withdrawn on the provider's side or the handshake never finished. The fix in almost every case is to reconnect the same account from the Integrations screen. Reconnecting takes seconds, and nothing you have already saved is affected.

Symptoms#

Any of these means a connection needs attention:

• The Google Search Console + Analytics card shows the badge Not connected when you know you connected it.
• The Google card shows Setup required instead of a Connect button.
• A panel that used to show measured Search Console numbers has gone back to AI estimates, and the Live data badge has disappeared from it.
• Viewing your Search Console properties returns an error line beginning Error: followed by one of not_connected, no_refresh_token, server_not_configured, or refresh_failed: and a reason.
• A social channel row shows Not connected after you connected it, or shows Setup needed.
• The channel list shows Could not load channels.
• Publishing to X fails with Your X connection has expired. Reconnect X and try again.
• A connection popup closes on an error page rather than returning you to the dashboard.

Diagnosis#

Connections live in one place. Go to Dashboard → Account & Team → Integrations and read the status on each card before changing anything. See How integrations work for how connections work in general.

Google Search Console and Analytics

The badge next to Google Search Console + Analytics tells you which of three states you are in.

If the badge says Connected but a report still shows no Search Console figures, click View my GSC sites. The response tells you which of the two layers failed:

Two things are worth knowing before you conclude the connection is broken:

• Search Console data lags. Performance queries default to ending three days before today, because Google does not publish the most recent days immediately. An empty last-72-hours window is normal, not a fault.
• Performance results are cached for one hour. If you fixed something in Search Console and re-ran a report straight away, you may still be looking at the previous hour's answer.

Social channels

Open Dashboard → Account & Team → Integrations and find the Connected channels card. Each of the six channels shows one of three states.

If the whole grid reads Sign in to connect your channels., your session has ended. Sign in again. If it reads Could not load channels., the request failed. Reload the page and try once more before reporting it.

If the connection popup showed an error

The popup renders the reason in plain language. These are the messages you can see, and what each one means:

Every one of these is safe to retry from the beginning. Nothing is left in a half-connected state.

Resolution#

Reconnect Google

1. Go to Dashboard → Account & Team → Integrations.
2. If the card currently shows Connected but is misbehaving, click Disconnect first and confirm at Disconnect your Google account? Real-data panels will revert to AI estimates.
3. Click Connect Google. You are taken to Google in the same tab.
4. Sign in with the Google account that owns the Search Console property, and approve the request. Metric Vault asks for read-only access to Search Console and Analytics plus your email address. It cannot change anything in your Google account.
5. You are returned to the dashboard. The badge should read Connected and show the Google address underneath.
6. Click View my GSC sites to confirm the properties you expect are listed.

If you see a Google warning screen during step 4, use the Seeing a Google warning? link on the card. It explains what the warning is and how to continue. See also Google connection problems.

Reconnect a social channel

1. Go to Dashboard → Account & Team → Integrations and find the Connected channels card.
2. If the channel shows as connected but is failing, click Disconnect. The button changes to Removing… while it works.
3. Click Connect. A popup opens on the provider's site.
4. Approve the request and wait for the popup to close on its own.
5. The row refreshes to show the connected account.

Complete the approval within 15 minutes. The handshake token is single-use and expires after that, which is the most common reason a second attempt is needed.

What reconnecting does and does not change

• Reconnecting replaces the stored permission. It does not touch your saved results, scheduled posts, monitored competitors or reports.
• Scheduled social posts that are still pending keep their schedule and send through the new connection.
• Disconnecting Google makes panels that had real Search Console figures fall back to AI estimates. No stored report is rewritten.
• Nobody is notified when you connect or disconnect. On a shared workspace, tell your teammates, because they see the same connections.

Prevention#

• Reconnect from the account that owns the data. A Google account with no Search Console property connects successfully and then shows an empty property list, which looks identical to a broken connection.
• Do not revoke Metric Vault in your Google or provider security settings unless you intend to disconnect. Revoking there leaves the dashboard showing Connected until the next refresh fails.
• Complete the consent screen rather than dismissing it. Skipping consent is what produces no_refresh_token.
• Expect to reconnect X periodically. X access tokens are shorter-lived than the others, and the publish step tells you plainly when it needs renewing.
• Check the channel state before a planned publish, not after. The Social Composer will not warn you in advance that a channel has gone stale.
• Remember Instagram and TikTok cannot publish text on their own. A post with no media returns a notice asking for media rather than failing as a broken connection. See Publishing and scheduling posts.
• Microsoft and GitHub are not connectable integrations yet. The entries on the Account screen link your sign-in identity; they do not import any data.