I've recently run into some issues with subscription notifications (example - "A new version of KB####### has been published") not triggering properly. I have a case open already trying to find a root cause and have continued to dig on my own. This has led me to diving into the Subscription table and it looks like there isn't anything that "cleans" up the data. For example, entries stay for inactive Subscribers or for no longer published versions of KB Articles. Right now I'm working through some scheduled Flows to get at least some initial cleanup done, but is anyone aware of anything out-of-the-box that should be doing this already? Alternatively, does anyone have any best practices to share of how they're also accomplishing this?
Thanks,
Erik
