Skip to content

Managing and Troubleshooting Sources

Once a source is connected, this is the page for the day-to-day operations: knowing what state a source is in, refreshing it, fixing failed syncs, and disconnecting cleanly. For first-time connection steps, see Connecting Sources.

Source status

On the Sources dashboard, a connected source shows whether it's currently refreshing (Mention is fetching the latest catalog from the provider — large workspaces can take several minutes) or idle (the asset list reflects the last sync). If a sync runs into trouble, the catalog simply won't pick up the latest changes — re-run a refresh, and if it keeps failing see Failed syncs below.

A web crawl has its own status on its detail page — pending, crawling, completed, or failed. Within a completed crawl, individual pages can end up imported, skipped (due to the depth or page limits you set), or unreachable (blocked by the site's policy, or an error loading the page). The detail page lists which pages came through.

Manual refresh

Sources also sync automatically on a daily schedule, but you can force a sync at any time:

  1. Open Sources from the admin sidebar.
  2. Find the source you want to refresh.
  3. Use the Refresh (or Sync now) action.

A manual refresh re-fetches the catalog from the provider and re-ingests anything that changed. Already-active assets that have been updated upstream are picked up automatically.

Failed syncs

If a refresh fails (the catalog stops picking up changes), the most common causes are:

  • Expired credentials — the OAuth token Mention uses has been revoked, expired, or had its scopes narrowed by the provider. Mention attempts to refresh tokens automatically, but some providers require the admin to sign in again.
  • Permission changes upstream — the account that authorized the connection lost access to content it previously had (for example, was removed from a Notion workspace or a Slack channel).
  • Provider outage — the upstream service is unavailable. Retry after the provider's status page reports recovery.

Reconnect to refresh credentials

If a manual refresh keeps failing, the simplest fix is to disconnect and reconnect the source. This re-runs the OAuth flow and refreshes Mention's stored credentials.

  1. Open the failing source from the Sources dashboard.
  2. Choose Disconnect and confirm.
  3. Connect the source again, signing in with the same account that has the right permissions in the provider.
  4. Re-activate the assets you want Mention to use.

(Disconnecting removes the source's synced assets, so you'll re-pick what to activate when you reconnect.)

If reconnection still fails, the issue is upstream — verify in the provider's admin console that the account can still access the content you expect.

Disconnecting a source

To remove a source entirely:

  1. Open the source from the Sources dashboard.
  2. Choose Disconnect and confirm.

Disconnection stops further syncs from that provider, revokes Mention's authorization, and removes the assets that came from the source. If you reconnect later, you'll re-discover and re-activate its content.

Web crawl re-runs

Web crawls do not have OAuth credentials, but they can fail if the target site changes structure, blocks the crawler, or returns errors. To re-run:

  1. Open the crawl from the Sources dashboard.
  2. Choose Recrawl on the crawl's detail page (or Delete to remove the crawl entirely).

A recrawl re-discovers pages from the configured root URL; review and activate the pages you want from the Inactive pages tab afterward.

When to escalate

Most sync issues resolve with a manual refresh or a disconnect-and-reconnect cycle. If a source repeatedly fails after that — especially if you can confirm the underlying credentials and content are healthy in the provider — contact support with the source name and the timestamp of the most recent failure so the issue can be investigated upstream.