Empty state for the dashboard when there are no runners assigned to the group

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Close this issue

Release notes

When there are no runners assigned to your group, no jobs have run so far, or no runners are active, metrics in the Fleet dashboard may be empty. We have replaced this with empty states that explain if user action is needed to show metrics.

Problem to solve

Multiple empty states are possible within the dashboard.

	Use case	What happens in the dashboard?	Can users take action to fix this?
1	No runners are assigned to the group.	No metrics can be shown in the whole page since we only provide metrics for runners that are assigned to the group.	Yes. Create group runners.
2	All runners are idle (they are not actively running jobs).	Runners will not be listed in the `Most active runners` panel.	No. Wait for runners to pick up jobs.
3	Runners did not run any jobs in the previous month.	No runner minutes will be reported for the previous month, so the `Runner usage` card will be empty.	No. Wait for the next month's report.
4	Jobs have not been triggered in the past 3 hours.	Job queue data in the `Wait time to pick up a job` panel will be empty since we only track the time it takes for runners to pick up a job in the last 3 hours.	Maybe. Trigger a job or wait for jobs to be triggered.
5	User upgrades their GitLab instance.	There will be no runner usage metrics from the previous month since we don't backfill it.	No. Wait for the next month's report.

Intended users

Platform engineers / group owners

User experience goal

The user should be able to understand why there are no metrics shown in the Fleet dashboard and if they specifically need to take action to make those metrics appear.

Proposal

	Use case	User experience proposal	UI text	Design
1	No runners are assigned to the group.	Show a page empty state when the user visits the Dashboard. Provide users with the action to create group runners.	View metrics for runner performance The group doesn't own any runners. Create some runners to view metrics like how long before a runner picks up a job, or which runners are most active.	no-runners.png
2	All runners are idle (they are not actively running jobs).	Show an empty state in the `Most active runners` panel.	All runners are idle right now. When runners pick up jobs, active runners appear here.	active-empty.png
3	Runners did not run any jobs in the previous month.	Show an empty state in the `Runner usage` panel.	No compute minutes were used in the previous month. If runners execute jobs this month, usage data will appear here.	usage-empty.png
4	Jobs have not been triggered in the past 3 hours.	Show an empty state in the `Wait time to pick up a job` panel. Add an action to view recent jobs (admin/jobs page).	No jobs were triggered in the past three hours. When jobs are triggered, the time they spend waiting to be picked up is shown here. View recent jobs	wait-time-empty.png

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited Sep 12, 2025 by 🤖 GitLab Bot 🤖