Check in your scheduled tasks. It may be that they put an exipiry on the action trigger. Your event logs should also show it executing.
It makes mention of calling a BAQ to import data on the DMT home page. I haven’t personally used it that way, but this is probably what the Auto DMT BAQ Load is referring to.
I am not in front of my work computer so don’t have a DMT.
The other thing the issue is, maybe the DMT is running, but it is throwing errors, or back in version prior to .45 there was a problem with running in -NOUI mode so if DMT is on that version and it is being executed through a scheduled task then that might be the cause.
One other note it is possible to run powershell using SQL agent so if you can’t find any evidence of the scheduled task in Windows Task Scheduler, it could be in SSMS as a SQL Agent Job, failing that they may have just had a batch file that they ran every day on their desktop, since they left they are not there to run it.
Finally be kind to the next person and when you fine the problem, please document it. 