Skip to main content
Qlty periodically analyzes your default branch to keep your project’s quality data up to date. This page explains how that scheduling works, how to adjust it, and how the data you see in Qlty relates to your repository’s current state.

​
How analysis frequency works

Qlty automatically analyzes your default branch on a recurring schedule. The default frequency is every 24 hours, but you can adjust it to match your team’s needs. The available frequency options are:
FrequencyBest for
15 minutesHigh-activity repositories where near-real-time data is important
30 minutesActive repositories with frequent merges
1 hourModerately active repositories
3 hoursStandard development pace
6 hoursLower-activity repositories
12 hoursRepositories with daily activity
24 hours (default)Most repositories
3 daysLow-activity repositories
7 daysRarely changing repositories
1 monthArchived or minimal-activity repositories
Higher analysis frequencies consume more analysis minutes.

​
Changing analysis frequency

To change how often Qlty analyzes your default branch:
  1. Go to Project Settings > General
  2. Under Default Branch Analysis, find the Analysis Frequency dropdown
  3. Select your preferred frequency
  4. Save your changes

​
Triggering analysis manually

You can trigger an analysis at any time without changing your frequency setting:
  1. Go to your project’s Builds page
  2. Click the Build button
This is useful when you’ve made an important change and want to see updated results immediately, without increasing your regular analysis frequency.

​
Understanding data freshness

The data shown on your project pages comes from two independent sources:
  • Analysis data: Generated by Qlty’s scheduled or manual analysis builds
  • Coverage data: Uploaded from your CI pipeline after running tests
Qlty merges the latest available data from both sources to display your project’s quality information. This means the data you see always reflects the most recently completed analysis and the most recently uploaded coverage report — which may not correspond to the very latest commit on your default branch.

​
Why data may not match the latest commit

Your repository on GitHub can receive new commits at any time — often faster than analysis and coverage processing can keep up. For example:
  • If your analysis frequency is set to every 24 hours, commits made during the day will not be reflected until the next analysis completes
  • If your CI pipeline takes 10 minutes to run tests and upload coverage, commits merged in the last 10 minutes will not yet have coverage data
Once a new analysis completes or new coverage data is uploaded, Qlty updates the displayed data within about a minute.
If you need fresh data for a specific commit, you can trigger a manual analysis rather than increasing your regular analysis frequency. This keeps analysis minutes usage efficient while giving you up-to-date results when it matters.

​
Deleted or renamed files

If you delete or rename a file in your repository, that file may continue to appear in Qlty until both a new analysis and a new coverage upload have been processed. Once both data sources have been updated with data that no longer includes the file, it will no longer appear.

​
See Also