(imported comment written by MattBoyd)
JonL, I definitely think we’re both seeing the same issue. I do see the “aborted” messages in the logs when this occurs. However, what I’m seeing is that the status of the aborted action becomes “Failed” and the remaining actions that are relevant continue to say “Waiting”. As I understand it, your remaining actions in the baseline say “Not Relevant” … correct? Our baselines are supposed to keep going if one of the actions fails. Also, they’re supposed to retry if the baseline fails.
It seems like the client isn’t checking if the baseline (or multiple action group… I use both terms interchangeably) was interrupted midway through, and it just gets stuck there. Do you have a support case open? I think this is a serious issue with the client. We depend very much on the baselines to reliably retry/continue when they fail.
PS - I thought I remembered someone else mentioning this issue, but I couldn’t find the post! Thanks for chiming in!