Thanks, and yes I'll raise a feature request. In regards to your suggestion, my script may need to process many subscriptions so spawning seperate runbooks may cause API limit issues plus negate any parralel time advantage with the need to start many runbook jobs. However I think this problem lends itself to a hybrid approach of breaking the subscription list up into smaller chunks and processing them in parallel where each job processes a smaller number of subscriptions sequentially. This will reduce the number of child runbooks. Thanks for the inspiration!
Thanks, and yes I'll raise a feature request. In regards to your suggestion, my script may need to process many subscriptions so spawning seperate runbooks may cause API limit issues plus negate any parralel time advantage with the need to start many runbook jobs. However I think this problem lends itself to a hybrid approach of breaking the subscription list up into smaller chunks and processing them in parallel where each job processes a smaller number of subscriptions sequentially. This will reduce the number of child runbooks. Thanks for the inspiration!