Helpful - yes! But unfortunately nothing that works for us that doesn't include writing custom implementations. I would expect, that AEM can do this out of the box - especially because there are multiple ways which should work, but don't respect the "include children" options for Tags.

Hi @aanchal-sikka ,thanks for your Answer! Unfortunately Option 1 and 2 don't work for us (see the other answers). Option 3 does not work, because we I didn't find a way to replicate a whole tree inside the Cloud Environments (it only works for single Nodes)

Thanks for your answer! Unfortunately, we can't use this approach, because we have some additional logic which hooks into the publish event, which we don't have if we publish the whole package at once.

Hi @AMANATH_ULLAH thanks for your detailed answer! Unfortunately this doesn't work. (See Thread with @lukasz-m above)

Hi @lukasz-m ,unfortunately, this doesn't work. The workflow ignores the children (even tough the parameter "-includeChildren=true". The workflow only publishes the selected root tag.Do you know a workaround for this?Thanks!

Don't know, if Adobe fixed this bug.

Hi, thanks for the answer!We have deployed many times prior to this event and never experienced this problem, nor have we changed the filters recently.I have double checked the filters and all of them seem correct.Neither is this issue reproducible with a new deployment. So i think it is seems unlik...