Support

No comment appearing on PRs

• Verify the Sherlog App is installed on the target repository (GitHub → Settings → Installations).
• Check that APP_ID, WEBHOOK_SECRET, and PRIVATE_KEY are set correctly in your deployment secrets.
• Confirm the deployment is running (Replit dashboard → Deployments).
• In your GitHub App settings → Advanced → Recent Deliveries, check that webhooks are being sent and receiving a 200 response.

License key not recognised

If you see "The Sherlog license key in .sherlog.yml was not recognised":

• Double-check the key is copied exactly, including case and any dashes.
• Ensure .sherlog.yml is at the repository root (not in a subdirectory).
• Verify the file format:

  license_key: "SHERLOG-PRO-XXXX-XXXX-XXXX"

• Keys are provisioned manually — contact support@alley21.dev to confirm your key is active.

Malformed .sherlog.yml error

Sherlog's YAML parser only supports flat key: value pairs. Avoid:

• Nested objects or lists
• Multi-line strings
• YAML anchors or aliases

Valid minimal example:

license_key: "SHERLOG-PRO-XXXX-XXXX-XXXX"

"Sherlog is at capacity" message

This means too many PRs opened simultaneously on this installation hit the per-installation concurrency limit (default: 5). Push a new commit to the PR to trigger a fresh analysis attempt.

If you see this frequently, the server operator can raise the limit via the SHERLOG_MAX_RUNS_PER_INSTALL environment variable.

"Sherlog hit an internal error" message

This indicates a bug in the Sherlog App. No action is needed on your part. Please email support@alley21.dev with:

• The Correlation ID from the comment (looks like xxxxxxxx-xxxx-…)
• The repository and PR number
• The approximate time it occurred

license_key: "SHERLOG-PRO-XXXX-XXXX-XXXX"