Unsynced Status Is Not Being Propagated Down The Lineage

[bolinzzz]

Hi team, we often use "Materialize unsynced" to bulk run downstream assets of a failed asset. However, after upgraded to version 1.8.10, we noticed that the unsynced status stops at the level one children, instead of propagating down the lineage graph. Please refer to the screenshot

• vouchers is unsynced because base__rewards__applied_voucher.. was updated after vouchers had run at 04:29.
• I would expect both recurring_dd_campaign and recurring_dd_campaign_aug_2024 to be labeled as unsynced.

Please shed a light on how to reinstate the old behaviour of "Materialize unsynced"

[cyberjar09]

we are affected too. Also on 1.8.10 OSS

[garethbrickman]

I think this was an intentional change in 1.8.0:

The “Unsynced” label on an asset is no longer transitive, i.e. it no longer displays purely on account of a parent asset being labeled “Unsynced”. This helps avoid “Unsynced label fatigue”, where huge portions of the graph often have the label because of a distant ancestor. And it also helps the asset graph UI load faster.