LogisterDocumentationSource lookup
GitHub App / Source lookup

Use attempted lookups to fix source mapping.

A connected repository is necessary, but source lookup also needs the reported stack path to map to a real file at a real Git ref.

Read the diagnostic

The attempted lookup shows repository, path, ref, and reason.

Example
taimoorq/newsfeedreader  app/app/controllers/feeds_controller.rb  main  not found

In that example, the doubled app/app path usually means the runtime path prefix or repository source root is adding app twice.

Fix order

Check the mapping before changing code.

  1. Open Project > Settings > Integrations > Source repositories.
  2. Confirm the repository is connected, not only synced.
  3. Click Sync repositories if GitHub App access, repository selection, or permissions changed.
  4. Set Runtime path prefix to the deployed prefix shown in stack frames, such as /app.
  5. Set Repository source root only for a real subfolder in the repo, such as packages/api. Leave it blank when source files are at the repo root.
  6. Confirm the default branch or event commit/ref contains the file.

Common symptoms

Most failures are mapping or ref mismatches.

MessageLikely fix
No source repository mapping existsSyncing is not enough. Connect a repository mapping for the project.
Mappings waiting for App accessInstall or link the GitHub App installation, accept permission changes, then sync repositories.
File was not foundCheck runtime path prefix, source root, default branch, and event commit/ref.
Wrong file or stale sourceSend repository, commit_sha, and branch from the SDK or CI deployment record.