Orchestration failing when a notification has no subscribers

Hi, I have an orchestration that invokes a notification under certain conditions. When I run the orchestration I get an error saying the notification must have at least one subscriber. I know it doesn't make sense to have a notification with no subscribers and I can subscribe myself to eliminate that error but I'm concerned once this is used in production that a user may unsubscribe from a notification leaving no subscribers resulting in the orchestration failing. Is there a way to eliminate this error or do we need to implement processes to ensure we never end