It started like any other alert. An issue was detected by Lumigo.
Service: prod_copilot_repo-parser_cont
Error Type: FailedToProcessGithubRepository
A notification popped up in Slack. Someone’s repository wasn’t processing correctly. Not a great way to start the day.
Nadav, a developer, jumped in first:
@Lumigo, what happened here?
Within seconds, Copilot responded with a full diagnosis:
@Nadav The prod_copilot_repo-parser_cont Lambda failed to process the GitHub repository REDACTED. The root cause is a 404 error from api.github.com when trying to get the repository installation information. This suggests that either the repository doesn’t exist anymore or the GitHub App is not installed on this repository. The repository status was updated to ‘index_failed’ in prod_copilot_traced-repositories.
Boom. No guesswork. No digging through logs. The exact cause of the issue surfaced instantly.
Now that they knew what had happened, Nadav needed more details.
@Lumigo, can you give me more details about the related users/projects?
And Copilot delivered the root cause.
@Nadav This issue occurred for project ID [REDACTED], which was trying to access the repository. The failure was triggered by a message from prod_copilot_github-events-queue.fifo. According to the DynamoDB record, before this, the repository was in ‘app_installed’ status, but the GitHub API now says the installation is no longer valid.
Translation: This repo was supposed to be set up correctly, but something changed—either the repo got deleted, or someone removed the GitHub App.
Nadav was getting closer to the root cause. Next step? Find out who this affected.
@Lumigo, can you search your traces to give me users of the project REDACTED ID..
Copilot didn’t just spit out logs—it connected the dots:
@Nadav Based on traces data, this project is accessed by:
And just like that, Nadav had everything he needed.
Lumigo Copilot delivered major time savings:
- Without Lumigo Copilot, debugging this issue could have been a nightmare
- Engineers would have wasted time digging through logs They might have missed key details, like which customers were affected.
- It could have taken hours instead of seconds to pinpoint the issue.
The Big Win: Faster Troubleshooting, Less Hassle
Instead of wasting time chasing logs, Copilot gave the team instant clarity:
- What happened (GitHub 404 error)
- Who was affected (Project ID, email addresses)
- Why it happened (Repo deleted or app uninstalled)
Lumigo Copilot didn’t just flag a problem—it solved the mystery fast.