Cosimo Damiano Prete

The opposite actually happens in case of timeouts (see https://github.com/codecentric/spring-boot-admin/issues/4516) where then the application is reported as up since a period X but then it's up since a period Y...

> fix for the issue: Please take a look: [#4872](https://github.com/codecentric/spring-boot-admin/pull/4872) I'm not a member of the team, therefore my review has little to no value at all. :D @SteKoe and...

Hello. Today I observed the same behaviour in our production instance with version `3.5.5`: What I observed is that in the journal the latest `STATUS_CHANGED` event is about the application...

Indeed, the `/applications` call triggered while loading the homepage is returning the latest available status for all the registered applications, which explains why the issue - UI wise - occurs....

If retries would be implemented in https://github.com/codecentric/spring-boot-admin/issues/4516, these would probably be beneficial for this as well. (maybe even solve it)

Hello. I can confirm the issue with version `3.5.6` as well. The homepage was reporting an instance as `UP` but its health status was reporting it as `AT WORK` (a...

Hello. I checked the docs and set the `default-timeout` to `30s`, but then I got the warning > 2025-07-29T06:53:27.193Z WARN 1 --- [Zookeepers Monitoring] [ main] d.c.b.a.s.c.AdminServerAutoConfiguration : Default timeout...

Hi @ulischulte. I saw that ticket and, while it kind of explains the rationale behind it, I must say I disagree with it. Personally, I would expect these interval-like jobs...

Any updates on this?

Hello @ulischulte. These random timeouts are becoming more and more problematic in terms of reliability of the solution. I've now an application that's reported as up since 1 hour when...