Once you set up your integration and import your repos, Flow must process your repos before you can see data in your reports. After this finishes, your repos are placed into the updating queue regularly to ingest and process new data. Learn more about the statuses you will see during these processes, how to troubleshoot issues, and how long processing usually takes.
Finding repository processing statuses
Use the Data status and Last updated columns on the Repos page to understand how your repos are updating.
The Data status column shows you the overall status of your repo. Statuses include:
- Processing: This indicates your repo is processing for the first time and Flow has not yet finished ingesting data for the first time from it.
- Healthy: This indicates your repo is processing normally and you don't need to take any action.
- Rate limited: The account connected to the integration has reached the allotted number of API calls set by the git or ticket host. Rate limits are temporary. Flow will continue to process the projects once the host resets the number of API calls. Larger projects are more likely to experience rate limits. To avoid unnecessary rate limits, use a dedicated service account to connect to Flow to avoid conflicts with API calls to the account from other systems.
- Failed: Your repo is no longer processing, and Flow has encountered an error. Click on the status for more information.
The Last updated column shows when your repo was last fully updated. If your repo has never been processed fully before, the column will be empty.
If you see a refresh icon next to the Last updated date, the repository is pending reprocessing. Once Flow brings your repo data into the system, it needs to run some additional preprocessing on the data to clean it up and make it ready for reports. This preprocessing runs every two hours. To see when data was last processed through this mechanism, use the Last reprocess date at the top of the Repos page.
If you are just getting started with Flow, 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. Learn more about repo processing time.
Troubleshooting
There are many reasons why a connection to your repository may have failed. Below is a list of some common reasons and solutions.
The repo has been deleted from your Git host.
- Solution: If your repo has been deleted from your Git host, delete it from your Flow account.
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, delete the blocked repo and re-import it under its new location.
The owner of the repo is no longer with the company.
- Solution: Update the credentials for the integration the repo belongs to. Use a service account to avoid lost access in the future.
The 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.
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, repository processing duration and frequency will depend on how much new data Flow receives.
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:
-
Use repo exclusion rules, like excluding archived repos, to only process the repos you want to see data for.
-
Don’t include binaries or large files in your repos. These take longer for Flow to process.
-
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.