Not sure if this is a design decision or not, but right now there is a performance issue caused when using the SubscriptionManager class where it waits on successfully completing the subscription handler in order to progress to the next subscribed event. This could be an optional feature or somehow elided into a background task (since it is already suggested to process subscriptions in a background task), but not sure how that affects the stability of using this issue

As a suggested work around, raw processing of the subscription queue (as noted here) allows flexibility to avoid these performance issues