Skip installation X times when conflicting process are running and then start to notify the user to close the application

We don’t want our users to spam them with too many toasts/notifications when we want to patch and the application is in use.

Could this idea be implemented?

If the upgrade process begins and encounters a conflicting process, it will automatically skip the update a certain number of times without providing any notifications (if it still encounters a conflicting process).

After skipping a certain number of times then notify user when it still encounters a conflicting process.

In this way the update will first be tried silenty and if there is user action needed, because the process is still running, then the user will be asked to close the process.