I do not believe that this has been corrected.
The issue I see is that using a baseline directly causes each patch in the baseline to action as a separate step.
Using the “Dynamically run baselines from site” step which basically looks for a baseline in a site. (this is how it should look)
And using the action that attaches directly to a baseline (which was recommended to me and how most of my Sa jobs are built)
When the 2nd SA job is run, it creates an action step for each baseline patch in the action listing, instead of a single action for the whole baseline. I do not know if the relevance is still affected, but last month this cause the relevance to break and send each patch in the baseline to each server in the action. ie 2019 patches were cached on 2016 along with the relevant 2016 patches, and sql updates were pushed to non-sql server (causing space issues).
If this is a new feature in Server Automation when directly using baselines in an action, then it is unusable in my context and breaks my SA jobs.
Edit: v9.5.58 dated 19/07/2021
Edit: Meh, I ended up rebuilding the bad SA jobs using step 137 (Dynamically run Baselines from a site), seems to work like old that way.