Invalid Device online/offline status between main Instances page and inside the machine page.

[pamudithaA]

Describe the bug
Login to new web portal and checking the online/offline status from the main Instances page show output as below.

Once we click in the instance, and go to the details page, we could still see device shown as online, though the last ping time quite old.

To Reproduce
Steps to reproduce the behavior:

1. Register a device in Landscape.
2. After a while, let the device go offline (by turning off the device).
3. Check the online/offline status in the main instances page and compare it with the details page of the instance.

Expected behavior
Consistent output across the web portal.

Screenshots
Attached above.

[yurii-vasyliev]

Thanks for the detailed report and screenshots, this is a valid inconsistency and we've reproduced the mechanics of it.

Some context on what's happening: the new portal derives online/offline in both places from the same data, the alerts returned by the API (an instance is shown as "Offline" when a ComputerOfflineAlert is present). The list page and the details page use the exact same component, so the divergence you're seeing means the two API calls (GET computers for the list vs GET computers/{id} for the details page) are returning different alert data for the same machine. The "Last ping time" field is display-only and doesn't feed the status.

We're tracking two follow-ups internally:

1. A backend investigation into why the single-instance endpoint doesn't report the offline alert while the list endpoint does.
2. A frontend hardening fix so the details page doesn't default to "Online" when alert data is missing - an unknown state should never render as "Online".

We'll update this issue as those land. Thanks again for flagging it.