I have noticed that ConfigSnapshot.Outdated does not trigger a property changed signal when the configuration updates.
When ConfigService pushes an update, the UpdateAvailable event fires correctly, and the Outdated boolean eventually reflects the new state. However, observing this change via GetPropertyChangedSignal("Outdated") yields no result; the signal simply never fires.
Note: In the attached video, I used SetTestingValue to force an update immediately without waiting for the cache refresh. However, I have also tested this with a real “Publish Now” update on a live configuration, and the result is exactly the same: the Outdated property signal never fires.
Expected behavior
While I am aware that listening to UpdateAvailable effectively covers the same use case as listening to the Outdated property change, the property signal should still function correctly.
For the sake of API consistency and standard engine behavior, developers expect properties to dispatch a signal when their values change. Currently, this specific property behaves inconsistently compared to other Roblox Instances