Reducing the max inhibition delay of 14 days of refresh awareness


The official documentation of refresh awareness ( states that updates will be postponed for up to 14 days if the app is running. This variable seems to be somehow hard-coded in the code of snapd:

For end users that don’t want to (or can’t) use the snap CLI or GUI to manually update the snap after closing the app, the update will be quite likely applied at the end of the 14 days (and might crash the executable at the same time).

I don’t want to argue on the current behavior of the refresh awareness, I would instead like to know if there is a way to reduce the inhibition period as the behavior will be identical for a user that doesn’t want to manually update the snap if the update is forced after 14 days or 2 days.