Repository processing statuses

Tags: Flow

Once you connected your repos to Flow, your repos will need to fully process, then every few hours they will be placed into the updating queue. Below are the different statuses you may see in this updating process.


Where do I find repository processing statuses?

To find the process status of a repo:

  1. Click Settings in the top navigation bar.
  2. In the left navigation under Integrations, click Repos.
  3. Locate the Last updated column. This column tells you when a repo was last updated.

back to top


Last updated column

The Last Updated column shows when your repo was last fully updated. If your repo hasn't fully processed for the first time, the date will be Never.

If you are just getting started with Flow, the reports will not load until at least one repo has been fully processed. Processing a repo can take anywhere from a few minutes to a few hours depending on the size and contents. Read more on repo processing time.

Fetching

If Fetching appears in the Last Updated column, your repo is being prepped to update. All your new data is being fetched for processing.

Processing commits

If Processing commits appears in the Last Updated column, your repo is actively being updated. 

Reprocessing pending

Once Flow brings your repo data into the system, it needs to run some preprocessing on the data to clean it up and get it in shape for reports. This preprocessing runs every two hours.

If you see a refresh icon next to its last updated date, the repository is pending reprocessing. You can find the Last reprocess time at the top of the repo page. If your commit data seems incorrect, allow time for reprocessing and check back later.

Updated

Once your repos have been updated, you will see a new Last Updated time/date.

Blocked repositories

Sometimes the connection to a Git host or repo becomes invalid. This could be an authentication issue or the repos could have been moved, renamed or deleted.

back to top


Troubleshooting

There are many reasons why a connection to your repository may have been lost. Below is a list of some common reasons and solutions.

The repo has been deleted from your Git host.

The repo has been renamed.

  • Solution: If your repo has been renamed in your Git host, delete the blocked repo from your Flow account and import it again under its new name.

The repo has been moved.

  • Solution: If your repo has been moved to another project in your Git host, you need to delete the blocked repo and re-import it under its new location.

The owner of the repo is no longer with the company.

  • Solution: If the blocked repo was imported by a user who is no longer with your company, transfer the repos to a new or existing Integration that has access and permission to these repos. For more information on transferring repos to another integration, see Managing repositories.

Owner’s permissions have been changed within the Git host.

  • Solution: Sometimes user permissions change within your Git host at the repo level. Double-check that the user has adequate permissions for the repo and try updating the repo again.

back to top


How long does it take for my repos to process?

Our system processes your most recent commits first and works in reverse chronological order.

In most cases, repos finish processing in anywhere from a few minutes to a few hours. In some cases, we've seen repos take up to a day or two, but this is unusual.

The time required varies based on the size of the repository, number of commits, and size of diffs. The initial pass can take some time. It's hard to say exactly how long yours will take because we haven't processed it yet.

The good news is that this is a one-time thing. The initial load is the most time intensive. After that, the repositories will refresh every hour.

How do I make processing my repos faster?

Flow takes longer to process repos when your repos are large or there is a significant number of them to process. Some repos may get stuck in a processing status. To avoid processing delays:

  1. Use repo exclusion rules, like excluding archived repos, to only process the repos you want to see data for.

  2. Don’t include binaries or large files in your repos. These take longer for Flow to process.

  3. If it’s not possible to exclude those files, leverage Git LFS (external site, opens in new tab) for file storage.

If you have a repo that has been in a processing status for longer than a few days, check to see if it is a large repo, then follow the above steps to reduce processing time. If this does not resolve the issue, reach out to Pluralsight support for additional assistance.

Note: Excluding specific files or file types for your repo from Flow does not reduce your initial processing time, since Flow first needs to process your repo to apply these rules.

back to top


If you need help, please contact Pluralsight Support.