Currently, when we update the state of an object, e.g. a Repository object, by polling its provider for updates, it will be marked as Stale=Unknown for the duration of the check.
This means that the condition will keep popping up during the validation cycle - even if there are no errors and the object is updated on schedule.
Instead, we can mark objects as Stale only if a certain amount of time has passed when no successful validation has been achieved. For instance, let's say we have a Repository object with a refresh interval of 5m - we can mark it as stale if the Repository cannot be successfully polled for changes for more than 10 minutes.
This ensures that conditions really do represent an error (or potential error) state.
Currently, when we update the state of an object, e.g. a Repository object, by polling its provider for updates, it will be marked as
Stale=Unknownfor the duration of the check.This means that the condition will keep popping up during the validation cycle - even if there are no errors and the object is updated on schedule.
Instead, we can mark objects as
Staleonly if a certain amount of time has passed when no successful validation has been achieved. For instance, let's say we have aRepositoryobject with a refresh interval of5m- we can mark it as stale if theRepositorycannot be successfully polled for changes for more than 10 minutes.This ensures that conditions really do represent an error (or potential error) state.