Query Regarding Execute Action Discrepancy in Add-On Setup

[kalyani1217]

I've configured an add-on setup where I'm retrieving feature states from the base setup and applying those states to the add-on setup features. However, there's a feature that wasn't installed in the base setup. Consequently, in the add-on setup, I've designated that feature as absent. Strangely, the execute action is being set to "none" instead of "REMOVE."

Planned feature: FeatureA, state: Absent, default requested: Unknown, ba requested: Local, execute action: AddLocal, rollback action: Remove
Planned feature: FeatureB, state: Absent, default requested: Unknown, ba requested: Absent, execute action: None, rollback action: None

For FeatureA, the execute action is correctly set to ADDLOCAL. However, for FeatureB, it's inexplicably set to None.

I've delved into the Wix source code and found that in the CalculateFeatureAction() function within msiengine.cpp, the execute action is only set to None if the requested state is unknown. In this case, the requested state is absent, yet the execute action remains None. What could be causing this discrepancy?