Fix a GitHub connection

I cannot see the GitHub connectionCopy Anchor Link

Confirm that you selected the workspace where the organization was connected, then open Workspace > Integrations and choose the connected account. GitHub integration details are available to workspace admins and owners. Ask a workspace owner to check the workspace and your role if the connection is still missing.

The organization or repositories are missingCopy Anchor Link

Check the repository access granted to the Sorena GitHub App in GitHub. The app can only provide Sorena with information it is allowed to access. An organization owner can review or update that access on GitHub. Then return to Sorena and request a sync if the option is available.

Sync is queued or unconfirmedCopy Anchor Link

Sync queued means Sorena accepted your request for background processing. If the status remains unconfirmed, choose Check sync status. Sorena keeps showing the last confirmed evidence until it can confirm a newer capture.

Sync failed or needs attentionCopy Anchor Link

The latest sync did not complete. The connection may still be in place, but its account details or repository access may have changed. If available, choose Sync data to try again. If GitHub access was changed or removed, restore the needed access on GitHub first.

If the message says Sync request was not queued, Sorena could not start the background request. The last confirmed evidence remains unchanged. Try again and check whether the new request is queued.

GitHub is limiting requestsCopy Anchor Link

Wait a little and retry. Repeatedly retrying while GitHub is limiting requests may not help.

Sync controls are disabledCopy Anchor Link

Wait while Sorena checks current sync activity. If it cannot confirm that status, use Retry sync status. A running sync or confirmed stale lock may require the recovery action shown on the page; follow manage sync operations before requesting another refresh.

If GitHub access is paused appears, restore the installation's access on GitHub. Sorena cannot reactivate it from the connection page. A disabled historical connection must be connected again from Integrations.

Still stuck?Copy Anchor Link

Open Help in Sorena with the workspace name, the time the issue occurred, and the status or message shown. Avoid copying filtered page addresses or private repository details. If you cannot sign in, email support@sorena.io. See how to contact support.