Integration troubleshooting

Summary#

Almost every integration problem is one of four things: the permission expired, the permission was revoked at the provider, the handshake did not finish, or the platform was never configured on the Metric Vault side. The messages tell you which, and three of the four are fixed by disconnecting and connecting again. This page maps every message you can see to its actual cause.

Symptoms#

Any of these means a connection needs attention.

On the connection screens

• A channel row reads Not connected after you connected it.
• A channel row reads Setup needed.
• The channel list reads Could not load channels. or Sign in to connect your channels.
• The Google card badge reads Not connected or Setup required when you expect Connected.

During a connection

• The popup opens on an error page instead of closing itself.
• The popup says Facebook or Instagram did not give Metric Vault access to any Page or account.
• The provider shows its own error page saying the return address is not allowed, often worded as "URL Blocked".
• The popup closes but the channel row does not change.
• The popup never opens at all.

When publishing

• A channel row in the composer results shows a reconnect message.
• Every channel fails at once.
• A scheduled post is marked Failed or Interrupted.

In reports

• A panel that showed measured Search Console figures is back to AI estimates and the Live data badge is gone.

Diagnosis#

The four causes#

Only the last one is out of your hands. Retrying it will not help and is worth recognizing early, because it looks identical to a failure you could fix.

Messages while starting a connection#

Messages while completing a connection#

None of these leaves a half-connected state. Every one is safe to retry from the beginning.

Messages when publishing#

Messages when reading Search Console#

Click View my GSC sites and the response identifies which layer failed.

Two things that look like faults and are not#

• Search Console data lags. Performance results end three days before today, because Google does not publish the most recent days immediately. An empty last-72-hours window is normal.
• Results are cached. Search Console figures are held for an hour, and every other data source has its own window. A change you just made at the provider will not appear instantly. See Result caching and freshness.

Resolution#

The reconnect procedure#

This fixes expiry, revocation and a failed handshake. It works the same way for every provider.

1. Go to Dashboard → Account & Team → Integrations. Google has its own card there, and social channels are in the Connected channels card.
2. If the connection shows as present, remove it first. Click Disconnect. For Google, confirm at Disconnect your Google account? Real-data panels will revert to AI estimates. For a channel, the button reads Removing… while it works.
3. Click Connect. Google opens in the same tab. A social channel opens a popup.
4. Approve every permission requested. Do not skip the consent screen.
5. For Facebook, Instagram and LinkedIn, choose the account posts should go to and click Continue.
6. Complete it promptly. Google's window is 10 minutes; the social window is 15.
7. Confirm the result. Google should show Connected with the Google address underneath. A channel row should show your account name.

Removing first is not optional busywork. A stale permission that is still stored is what makes the interface report a connection that does not work.

If the popup will not open or will not close#

• Allow popups for metricvaultai.com. The connection cannot complete in a blocked window.
• If the popup closed but the row did not update, click on the dashboard window. The list refreshes when the window regains focus. Reloading the page also works. Some browsers deliberately cut the link between a popup and the page that opened it, and the focus refresh is the fallback for exactly that.
• Do not refresh the popup mid-flow. The handshake is single-use and a refresh spends it.

If a permission was revoked at the provider#

Revoking Metric Vault in Google's account permissions, or in a platform's connected-apps settings, does not tell Metric Vault anything. The card keeps saying Connected until the next use fails. Disconnect here as well, then reconnect if you still want the connection. See Disconnecting an integration.

If the row says Setup needed#

Stop. That platform is not configured on the Metric Vault side, and no amount of retrying will change it. Contact support and name the platform. See Contacting support.

For support: an administrator can confirm which credentials are missing and the exact return address to register with the provider using the social diagnostic described in Diagnostic endpoints.

If a scheduled post failed or was interrupted#

A Failed post is not retried automatically, and cannot be edited. The reason is listed under the post: each channel that did not take it, with the platform's message, or a single error that stopped the whole post. Fix the cause, then schedule a new post.

An Interrupted post was cut off while it was being sent. Some channels may already have it. Check the channels before posting again, then press Cancel on the row. See Scheduled social posts.

Prevention#

• Expect to reconnect Facebook and Instagram about every sixty days. Meta offers no renewal. X, LinkedIn and TikTok renew themselves when you publish, as long as the platform issued a renewal token, and a Threads connection used at least once a month keeps itself connected.
• Check channel states before a planned publish, not after. The composer does not warn you in advance that a connection has gone stale.
• Complete the consent screen rather than dismissing it. Skipping consent is what produces no_refresh_token, which looks like a connection but cannot renew itself.
• Connect 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 is indistinguishable from a broken connection at a glance.
• Keep your Page selected on Meta's consent screen. Facebook and Instagram connections are refused when the login returns no Page or Instagram account.
• Choose the account deliberately on the account list. Posts go to the one you pick.
• Do not revoke at the provider unless you intend to disconnect. If you do, disconnect here too so the interface stays honest.
• Tell your teammates when you disconnect Google. They see the same connection, and nothing notifies them.
• Attach an image for Instagram, and do not send posts to TikTok. Those messages are the product working correctly, not a connection fault.
• Reconnect from the same browser profile you are signed into. Connecting while signed into a different provider account in that browser attaches the wrong account.

For Google-specific diagnosis, including missing properties and the unverified-app warning, see Google connection problems. For the symptom-first version of this page aimed at a reader who does not yet know it is an integration problem, see An integration stopped working.