I have an FME workspace that I have set to run on a scheduled day/time etc through the Windows Task Scheduler. This worked fine, but recently the following happens:

• the workspace does start to run, but gets stuck at some point while reading the data (Usually 3 minutes in to a workbench that runs about 30 minutes normally)
• this is more or less at the same point in time where FME creates a ffs logfile.
• the task scheduler doesn't show that the task failed, it shows that everything went fine (task result = (0x0))
• the regular workspace logfile just shows the process stuck somewhere at reading something that does issue a warning. I checked and the workspace is set to keep running through warnings. Like I mentioned, everything used to work fine.

The machine we run it on is an Azure machine. The tasks is set to run on a time when I'm normally not logged onto the machine. When I do log on to the machine and run the task manually on the task scheduler, everything seems to work fine.

Because of all of the things listed in the above, the fact that nothing changed on the side of FME regarding the workspace and the fact that everything used to work fine before, I am going to assume that some user settings changed on the Azure machine.

However, what do I tell my IT department? Which user settings do they need to set, and to what settings?