I'm running an Angular app that uses SwPush requestSubscription() to generate browser sub links and store those in a database for each user that allows Notifications. When my other db driving the data behind my app's dashboard gets updated, it fires off a trigger to an AWS Lambda function, which in turn uses web-push sendNotification() to show a Notification to each subscribed user about what changed. The Angular service worker shows them as expected when the tab itself is open or closed as long as my browser is running, and does not show Notifications when my browser is closed.
However, if any Notifications were sent to my sub link while my browser was closed, they all immediately show at once the next time I open my browser. I don't want them to be "stored up" like this and shown all at once - if the browser is closed, don't worry about showing Notifications at all on next reopen.
I know SwPush has its own listeners and will fire off events when Notifications are to be received, but by the time I open the browser, the Lambda has already triggered and fired off all the sendNotification() calls.
Is there any setting/option to change within the Angular service worker, the SwPush library, or the web-push library in order to accomplish this?