Yes, I can confirm it works now as intended on my machine. Do you mind telling me what caused the issue?
A bug in saving exchange data update interval, which was introduced in the latest version, which I inadvertently introduced after testing, while packaging gadget for release. Pretty lame actually.
