Impact GateReference
Troubleshoot common issues
Resolve sign-in failures, missing repositories, partial indexing, and missing or outdated PR reports.
On this page
Start with the current state#
- Use the canonical site at impactgate.in and confirm the selected workspace.
- Refresh the affected page and read the visible error or job status.
- Confirm that the installation is active and the intended repository is selected.
- Check Coverage and the indexed SHA before investigating missing findings.
- For a PR, compare the report's analyzed head with the latest commit.
Sign-in problems#
| Symptom | Next action |
|---|---|
| Google popup blocked or closed | Allow popups for impactgate.in and try again, or use a passwordless email link. |
| Sign-in email has not arrived | Check the entered address and spam folder, then request a new link if needed. |
| Email link invalid, expired, or already used | Request a fresh link and open the latest message. |
| Confirm your email after opening a link | Enter the same email address that received the link, then Complete sign-in. |
| Account exists with another sign-in method | Sign in using the existing method, then link an enabled provider from Settings. |
| Session expired or revoked | Sign in again using the account that has workspace access. |
| Browser could not retain the session | Allow site storage for impactgate.in, then reload and sign in. |
GitHub installation or repository missing#
Check the GitHub account
Authorize the personal GitHub account that owns or administers the organization installation. Verify which account is signed in on github.com.
Check pilot access
Ask your deployment owner whether this organization is enabled. An App installation for an unapproved organization is unavailable to this deployment.
Check installation permissions
In the intended organization's installed GitHub Apps, confirm Impact Gate is installed, active, and granted the relevant repositories. Archived or disabled repositories are not offered for selection.
Reconnect
Use Manage GitHub connection or Manage connection in Settings and refresh installations. Complete the flow in the same browser before it expires.
Refresh repository selection
Open Select repositories again after access changes. Save the intended selection before expecting analysis.
If connection expired, was canceled, or could not be verified, start a new connection from Impact Gate. Reusing an old callback URL will not complete authorization.
Indexing is partial, failed, or missing APIs#
| Symptom | Next action |
|---|---|
| No endpoints discovered | Confirm a supported OpenAPI 3 document is committed on the indexed default branch. Inspect Coverage. |
| Missing or invalid contract | Correct document syntax, paths, and local references, commit the change, then Re-index. |
| Consumer repository marked partial | Read the notes. A missing provider contract does not by itself prevent supported static caller extraction. |
| Unsupported language or file budget | Treat the recorded snapshot as partial; repeated indexing does not expand supported extraction. |
| Failed after GitHub access changed | Restore repository access, reconnect if needed, then Re-index. |
| Queued or running for an unusually long time | Inspect the latest job phase and error; ask the deployment owner to check worker health if progress remains stalled. |
A PR has no report#
Confirm analysis scope
The repository must be selected in the connected workspace, indexed, and accessible to an active App installation. The PR must be open.
Look for the check
Find Impact Gate in GitHub's checks. A comment can be absent when Publish findings as pull request comments is disabled, even when analysis ran.
Check background jobs
Open Engineering overview or Repositories and inspect Analysis jobs. Read a failed job's error before requesting more work.
Allow recovery to scan
Eligible open PRs are checked periodically for missed deliveries, including PRs opened before indexing finished. Larger selections are scanned in batches.
Ask for delivery diagnostics
If no job appears, give the deployment owner the PR URL, repository, current head SHA, and approximate time. An App owner can inspect webhook activation and recent GitHub deliveries.
You do not need to repeatedly open new PRs to recover a missed delivery. Failed jobs are not retried indefinitely by the open-PR scanner; unresolved worker or authorization failures need attention.
Results are outdated or unexpected#
| Symptom | Next action |
|---|---|
| Report shows an older head | Wait for the new-head job, then refresh GitHub. Superseded work must not replace a newer report. |
| No finding for a source-only route or behavior change | Review whether OpenAPI changed too. Provider implementation drift is unverified. |
| No known caller for a used API | Confirm the consumer is selected, indexed, and written in a supported pattern; verify usage outside static scope. |
| Dependency points to an unexpected service | Inspect the path-based reference and host configuration; deployment host association can be unverified. |
| Dashboard has not refreshed | Close open dialogs and return to the active tab, or reload to fetch the current snapshot. |
| Settings changed while editing | Refresh Settings, review the current values, then reapply and save the intended changes. |
| Review belongs to a previous snapshot | Open the updated evidence and mark reviewed for the current snapshot. |