The specification for Blendedness in the Object table is:

    Blendedness:

        functor: Column

        args: base_Blendedness_abs_flux

        dataset: meas

and it looks like Scarlet doesn't make a base_Blendedness_abs_flux column. It does make:

['base_Blendedness_abs',
'base_Blendedness_abs_child_instFlux',
'base_Blendedness_abs_child_xx',
'base_Blendedness_abs_child_xy',
'base_Blendedness_abs_child_yy',
'base_Blendedness_abs_parent_instFlux',
'base_Blendedness_abs_parent_xx',
'base_Blendedness_abs_parent_xy',
'base_Blendedness_abs_parent_yy',
'base_Blendedness_flag',
'base_Blendedness_flag_noCentroid',
'base_Blendedness_flag_noShape',
'base_Blendedness_old',
'base_Blendedness_raw',
'base_Blendedness_raw_child_instFlux',
'base_Blendedness_raw_child_xx',
'base_Blendedness_raw_child_xy',
'base_Blendedness_raw_child_yy',
'base_Blendedness_raw_parent_instFlux',
'base_Blendedness_raw_parent_xx',
'base_Blendedness_raw_parent_xy',
'base_Blendedness_raw_parent_yy',]
}}

Will you take a look at the schema definition in Scarlet and double check that "base_Blendedness_abs" most accurately matches what base_Blendedness_abs_flux was providing?

From the table schema:"base_Blendedness_abs", "Measure of how much the flux is affected by neighbors: (1 - child_instFlux/parent_instFlux). Operates on the absolute value of the pixels to try to obtain a "de-noised" value. See section 4.9.11 of Bosch et al. 2018, PASJ, 70, S5 for details."

I was unable to find the base_Blendedness_abs_flux column in table schema going back to 2019 to compare this to.

For future readers, just confirm that base_Blendedness_abs is fine.