Skip to content
Metric VaultHelp Center
Open app

Integration troubleshooting

Every message a connection can show you, what each one actually means, and the reconnect procedure that fixes almost all of them.

Last updated 2026-09-16

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 connection ends on an error page instead of returning to Integrations.
  • The connection page 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".
  • You come back to Integrations but the channel row does not change.
  • The platform keeps showing its own sign-in page.

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#

CauseHow you recognize itFixable by you
The permission expiredA publish attempt returns Your <platform> connection has expired. followed by an instruction to reconnectYes
The permission was revoked at the providerEverything looks connected until the first use failsYes
The handshake did not finishThe connection ended on an error pageYes
The platform is not configured on the Metric Vault sideThe row reads Setup needed, or the connect attempt reports the platform is not set up yetNo. Contact support

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#

MessageMeaning
<Platform> is not set up yet. followed by setup instructions for an administratorThat platform is not configured on the Metric Vault side. Contact support
Sign in to continue.Your session could not be verified when you pressed Connect. Sign in again and retry
Could not start the connection. Please try again.The connect link could not be created. Retry
This connection link has expired or is not valid. Please start again from the dashboard.The single-use connect link was already used or is older than 15 minutes. Press Connect again
Unknown platform.The connect request named a platform that does not exist. Start again from the channel row
Could not start the connection.A server-side failure before the provider was reached. Retry
Google OAuth is not yet configured. followed by setup instructionsGoogle sign-in is not configured on the platform. Contact support
Could not start the Google connection, please retry.A transient failure. Retry

Messages while completing a connection#

MessageMeaning
<Platform> denied the connection: followed by a reasonYou declined, or the provider refused. Usually a permission you did not approve
This connection link is invalid or was already used. Please start again.The handshake is single-use and was already spent. Refreshing the page mid-flow, pressing Back, or opening the link in two tabs does this
The connection flow expired (over 15 minutes). Please start again.More than 15 minutes passed between clicking Connect and approving
The connection response was missing its code or state. followed by diagnostic detailThe provider returned an incomplete response. The detail in brackets is for support
The server is missing credentials for <Platform>.Configuration changed between starting and finishing. Contact support
Could not reach <Platform> to complete the connection.The provider was unreachable. Retry in a few minutes
The connection could not be completed: followed by a reasonThe provider refused the final exchange. The reason is theirs
Facebook did not give us access to any Facebook Page. followed by what to checkThe login returned no Page, so there is nothing to post to. Nothing was stored. Check you are signed in to Facebook as the person who manages the Page, reconnect, and keep the Page selected on Meta's screen
Instagram did not give us access to any Instagram account. followed by what to checkInstagram accounts are found through the Facebook Page they are linked to. The account must be Business or Creator, and linked to a Page on this login
Facebook signed you in, but we could not read which Facebook Pages you manage followed by a reasonMeta did not answer the lookup. Nothing was changed, and any existing connection is untouched. Retry in a moment. Instagram has the same message about Instagram accounts
Pick an account first.Continue was pressed on the account list with nothing selected
This connection expired. Please start again.The account list sat open for more than 15 minutes
That account was not one of the options.The choice did not match the list that was offered. Start again
Invalid or expired connection request. Please start again.The Google equivalent of a spent handshake
OAuth flow expired (> 10 min). Try connecting again.Google's window is 10 minutes, shorter than the 15 for social channels
Token exchange failed: followed by a reasonGoogle refused the final exchange. A reason mentioning the redirect address means the return URL is not allowed on the Google side. Contact support

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

Messages when publishing#

MessageMeaning
The connection to this channel has expired. Reconnect it and try again.The stored permission is no longer accepted and could not be renewed. Meta connections last about sixty days. Reconnect, then Retry failed
This channel is no longer connected. Reconnect it, then retry.The connection was removed after the post was created
Publishing did not confirm. Check the channel before retrying, because the post may already be there.The connection dropped as the post was published. The channel shows Check channel. Look before you retry
A file in this post is no longer available. Remove it and add it again.A file the post uses was removed from the media library
Instagram could not process this post. Check that the file meets the Instagram requirements, then retry.Instagram refused the file after upload. The composer's checks cover the published rules; this is a rule Instagram applies on its side
Instagram is still processing this post after 20 minutes. Retry later.The same wait also applies on Threads. LinkedIn and TikTok give up after 15 minutes
No Instagram account is linked to this connection. Reconnect Instagram.The Instagram Business account is no longer linked to the Page the connection used
LinkedIn did not return an account id when this channel was connected. Reconnect LinkedIn.The identity lookup did not complete during connection. Threads has the same message
LinkedIn will not let this app post as a company page yet. followed by an explanationA company Page was chosen and LinkedIn refused. Reconnect and choose the personal profile
X did not accept the upload. and similarThe platform refused a file. The platform's own reason is shown instead when it gives one
The channel refused the post.The platform refused it and gave no reason
This tool needs a paid plan. Free includes the 13 technical SEO tools; upgrade to Pro to unlock the rest.Publishing is not included on the Free plan. This is not a connection fault

Problems the composer catches before publishing, such as a PNG going to Instagram or a post over X's 280 characters, are shown on the channel with the fix and never reach the platform. The full list is in Publishing and scheduling posts.

Posts scheduled with the earlier composer, before 2026-09-16, still report in its wording, for example Your X connection has expired. Reconnect X and try again., Not connected. Connect <platform> first. and No Facebook Page found on this account. Posting requires a Page you manage.

Messages when reading Search Console#

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

MessageMeaningFix
not_connectedNo stored Google permission for your accountConnect Google
no_refresh_tokenGoogle issued a short-lived permission with no way to renew it. Happens when Google reuses an earlier consent instead of asking againDisconnect, connect again, and complete the consent screen
server_not_configuredGoogle sign-in is not configured on the platformContact support
refresh_failed: followed by a reasonThe stored permission was revoked or expired at Google's endDisconnect and reconnect

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 and every social channel open in the same tab.
  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 platform keeps asking you to sign in, or the row does not update#

  • A sign-in page on the platform belongs to the platform, not Metric Vault. Connect opens the platform in the same tab. If LinkedIn, X or Meta shows its own sign-in page, this browser is not signed in to that platform. Sign in there once and approve; nothing in Metric Vault can skip that step.
  • If you came back but the row did not update, reload the Integrations page. The channel list is read fresh each time the page loads.
  • Do not refresh or press Back mid-flow. The handshake is single-use and either one 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.

See also

Was this article helpful?