Troubleshooting

A repository is missing

Confirm the Lore GitHub App installation includes that repository and your GitHub account has read access. Refresh your GitHub connection after changing the selected repositories. Allow up to five minutes for cached permissions to refresh.

A scan is waiting or paused

Check Repositories and Activity. Queue priority depends on the plan. A plan_limit status means the Free plan needs an available repository slot or an upgrade. Repeated failures can pause scanning; resolve the underlying access issue before using the repository's resume or scan controls.

An agent cannot connect

Check that the URL ends in /mcp and the client supports Streamable HTTP with OAuth. Complete browser authorization, including SSO if required. Reconnect after a token has been revoked. Test list_repos from the agent itself.

An OAuth discovery error happens before a tool call. Record the exact error and client version for support; do not send access tokens or authorization codes.

A scan completed without a cleanup PR

Check Memory for extracted facts. Some sources provide context without eligible code changes. Protected notes, documents, and discussions may remain in place.

A fact is inaccurate

Follow its evidence links. If you have write access to the repository, edit the fact or retire it with an explanation. Source evidence is the basis for review.

Contact support

Use Support in the dashboard. Include the repository name, approximate time, client version, and error message. Exclude credentials and private source code.