Yes, I did notice something interesting for the only Eset provided scheduled scan that is time-dependent; log maintenance. This time format coding along with an interval of "0" is what I am coding to try in my user created scheduled scan to see if it resolves the issue.