Had a client in our datacenter who installed SEPP on all of his customer webs servers, and due to network design constraints, they could not communicate with each other and so the SEPP manager was not installed. Scan jobs were setup. After a while we noticed that the jobs only ran when we were logged in to do the maintenance. Seems jobs are starten unde the logged in username/session, not the system account.
We worked around it by always keeping at leest ons session active; not 'log off' but 'disconnect'
Might be different in the latest versions of SEPP though, haven't tested that