Once you have connected your repos to Flow, your repos will need to fully process, then every 2-3 hours they will be placed into the updating queue. Below are the different statuses you may see in this updating process.
Who can use this?
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.
If Fetching appears in the Last Updated column, your repo is being prepped to update. All your new data is being fetched for processing.
If Processing commits appears in the Last Updated column, your repo is actively being updated. It will stay in this state for a few hours during initial processing and depending on the number of recent commits, it could be in this state anywhere 5-30 minutes.
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 off, allow time for reprocessing and check back later.
Once your repos have been updated, you will see a new Last Updated time/date.
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.
How do I know if my repository is not updating?
You can see all repo connectivity issues when viewing your imported repos. On your Flow home page, go to the top navigation bar and click Settings. Using the left navigation under Integrations, click Repos.
Once you're on the Repos page, if any of your repos are not updating you will find an alert under the Status column next to the repo. You will also see alerts on the individual repo page. There are two alerts you might see.
- Unable to update repo: If you see this error, it means that the most recent attempts to update your repos, have not been successful. The Last Updated date will reflect the last time the repo was fully updated.
- Blocked Repos/Error Processing Repo: After multiple failed attempts to update your repo, due to a lost connection, the repo will be blocked and contain the following error message Error processing repo. Please contact support.
Troubleshooting Blocked/Unable to Update Repositories
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.
- Solution: If your repo has been deleted from your Git host, you then, can simply delete it from your Flow account.
The repo has been renamed.
- Solution: If your repo has been renamed in your Git host, you will need to delete the blocked repo from your Flow account in order to import it again under it’s new name.
The repo has been moved.
Solution: If your repo has been moved to another project in your Git host, you will need to delete the blocked repo and re-import it under its new location.
The owner of the repo is no longer with with the company.
Solution: If the blocked repo was imported by a user that no longer exists within your company, you will need to 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.
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 intense, and after that the repositories will refresh every hour.
If you need help, please email firstname.lastname@example.org for 24/7 assistance.