Member actions not stopped when baseline action is stopped

Customizations
1

(written by JesperLarsen)

Can someone please confirm this:

I create a baseline, and adds a component to it.

I then take a custom action w. that baseline, and see it show up in the Management Console.

I can then see the action is open by using the below query, and i can see the sub-action is also running:

> https://master:52311/api/action/233739/status
> 
> https://master:52311/api/action/233740/status

I then stop the baseline-action again, and the status says Stopped… but the underlying action say still open??

I then delete the baseline-action, and the status still says Stopped… and the underlying action say still open??

erhhmm… so the sub-action is stilll… open?

2

(written by JesperLarsen)

Ouch… the sub-actions are STILL available after deleting the parent action and running the

BESAuditTrailCleaner-3.0.10.77 -O

So, when I delete a baseline-action, I’m supposed to stop/delete all child-actions too??

3

(written by jgstew)

I have not investigated this, but you should not need to stop/delete child actions as well. I’m not sure if what you are seeing is expected behavior or not, but it doesn’t sound right. ( perhaps the child actions stay open, but don’t actually do anything ? )

4

(written by RobG1)

This also appears to be true for multiple action groups. My code is creating a mag and uploading it. After it goes complete, when I delete the mag, all the member actions still appear to exist in an open state.

If I delete the mag, the status for the mag shows something like this,

/api/action/4006/status

4006Stopped40074008

If I look at the status of a particular member action it shows open,

/api/action/4007/status

4007Open