Sign in or sign up before continuing. Don't have an account yet? Register now to get started.
Register now

ci-runners last contact ambiguous/not always updated

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

  • Close this issue

Summary

image

Steps to reproduce

visit https:///admin/runners

Example Project

N/A

What is the current bug behavior?

Indicates last contact of at least 19min while 2 of them actually pinged gitlab within the last minute (confirmed by Runners with last contact more than a minute ago: 2)

What is the expected correct behavior?

Last contact should be less than a minute in case it is. The current field seems to indicate the last time the runner was involved in a job; which can be very useful info, but shouldn't be under the "last contact" title

Alternative expected behavior: rename the last contact column to what it actually reflects (last activity?) and give some visual indication that gitlab hasn't heard from the runner in over a minute ("lost contact"); f.e. by using a background color

Relevant logs and/or screenshots

See summary

Output of checks

N/A

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited Jun 19, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading