Just querying, is this something which will be resolved relatively soon (is it actively in the pipeline), given that using the new provider/agent still has the bug and it’s not just legacy plug-in agents? Or is this like a “It’s in the backlog, one day it’ll probably be sorted”
