Git and repository errors

Common Paradime errors related to Git providers, repository access, and pull request lineage generation.

Use this page for errors tied to Git provider availability, repository access, or PR-based workflows.

PARA-1003: Could not read from remote repository on GitHub

Paradime could not fetch your dbt repository from GitHub.

This usually happens when the GitHub API is down, overloaded, or temporarily unresponsive.

Most cases are intermittent.

Solution

• Check GitHub Status.

• If GitHub reports an incident, wait and rerun the job.

• If you need results immediately, trigger the job manually.

PARA-1008: Couldn't connect to git repository

Paradime could not connect to the repository attached to your workspace.

Common causes include:

• The repository no longer exists.

• The deploy key was removed.

• The account that added the deploy key no longer exists.

Solution

Confirm the repository still exists.

Confirm the SSH connection between Paradime and your Git provider still works.

If needed, reconnect the repository using GitHub or your provider's equivalent setup flow.

PARA-1013: Couldn't generate Lineage Diff report

Paradime could not generate the Lineage Diff report for a pull request.

This usually means Bolt is not fully configured.

At least one active production schedule is required.

Solution

Create and activate a production schedule.

Start with Creating Schedules and 1. Schedule Settings.

If the issue continues, contact support.