Admin · Allow about 12 minutes
Before you begin
Owner or Admin with the relevant integration available for your subscription and environment. Have provider access to the intended sources. A Coming soon service is not an active connection.
1. Identify the failing stage
Open Integrations and select the affected service. Check connection status, selected sources, destination knowledgebase, and any import or sync history.
Follow the provider’s Connect → Sources → Preview → Import drafts → Review flow. Record which stage failed and the displayed error.
Use Refresh progress on an active import to read its latest status. Queued or Retry scheduled is different from a completed import or a terminal failure.
2. Correct access and retry supported work
If reconnection is required, have an authorised Admin use the provider’s Connect or Reconnect action and check the account and source permissions. Never paste provider tokens into articles or support messages.
If source preview fails, check that the selected folder, space, or document still exists and is shared with the connected account. Retry or refresh preview where offered.
For Google Drive import failures, review the updated plan and use Import remaining drafts and retry failures when available. Google Drive imports run in batches of up to 25 documents per folder; continue while supported documents remain pending.
Use Pause or Resume only where offered on the connection. Pausing incoming work does not by itself remove existing Beetl articles or retract their published versions.
3. Resolve local conflicts and verify
Open the imported-content review queue and inspect conflicts against the current local draft. Preserve local editorial changes before making a decision.
Review the article and its Beetl access settings; source permissions are not inherited. Where appropriate choose Keep reviewed draft connected, or Keep local and detach to stop incoming changes for that document.
Confirm the decision succeeded and inspect the imported draft in Content Manager. Publishing remains a separate article action.
If the problem persists, provide the service, failing stage, time, and non-sensitive error to support. A provider that is unavailable in your environment may require an exported-file import instead.
Check your result
You know the failing stage, have verified the corrected draft or a safe detached local copy, and have not mistaken import approval for publication.
If something goes wrong
Repeated authorisation failures: ask the provider administrator to check the connected account and source permissions before reconnecting repeatedly.
Import is waiting: check for an active job or scheduled retry. Refreshing the page reads status; it does not force the worker to complete.
Local edits conflict with source changes: inspect the reviewed draft and choose deliberately whether to keep the connection or detach; do not retry blindly.
No import action is available: check service readiness, selected sources, destination access, preview warnings, and whether the plan has changed.