Multiple Action Group is completed, but Sub-Actions are on 'Waiting'

(imported topic written by Harald.Zarakowitis)

Hi,

I have a Multiple Action which status is “Completed”, but some Sub-Actions are still on “Waiting” (compare attachment).

How is this possible?

Regards,

Harald

(imported comment written by SystemAdmin)

Hi Harald,

I think you are seeing a known bug that you can hit in a corner case. If you deploy a multiple action group (MAG) with a post-action restart on it then you may hit this situation. After the BES Client has run each of the actions it will attempt to do the restart which may involve displaying messages to the user. There is now a period of time between when the client initiates the restart and the computer going down during which the BES Client will be evaluating data. If the BES Client evaluates your sub-actions during this interval it can cause the action status not to update correctly after the reboot. The BES Client basically forgets that it needs to report the final status for these actions and doesn’t go back to report them.

This should only happen if the actions were actually successful. So, if the computer is in this state is safe to assume the actions actually worked correctly. You can also look at the source Fixlets to double check, the source Fixlets should no longer be relevant if the action was applied successfully.

Hope this helps!