The way I would start looking for this is by using the Design Synopsis feature to generate a listing of all agents in the NSF file for the application. You can search that listing for the name of the folder. If you find a hit, backtrack a bit in the listing to find the name of the agent.
The thing is, this job could be running as an agent in any database, not just the one where the data resides. (I have often designed systems with "Agent Container" databases.) The job could also be running on an ETL server somewhere else on the network, or it could be running as a script launched by the operating system's scheduler elsewhere on the network. Hopefully, it's not one of those things, but even if it is in an agent in the target NSF file, you still might not find the folder name. The agent could be reading the folder name from a profile document in the NSF file, or from a configuration document in some other NSF file.
But that's where I'd start.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…