This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
When I've used the job, I first run it on the server to get it configured correctly. Then I schedule it to run on the server and output the data to a network disk. I prefer to break the job up into the MongoDB dump and then to have a second job which does the calculations and exports. The data can be read and potentially used to create new value (e.g. telemetry data) without the need to have access to Mongo.
If the "authentication" doesn't work when you're logged into the server, that is clearly 1 issue. If you can't schedule the job (running on a different server), then you need to force the job to the server.
Alteryx ACE & Top Community Contributor
Chaos reigns within. Repent, reflect and reboot. Order shall return.