Myself and my colleagues were logged out of our sandbox CRM environment (we think it may be due to our recent Salesforce stage refresh) and when I logged into DemandTools there was a warning message at the top of the page stating "Your Org "e.g. org name Stage" (ID number) has been logged out due to an invalid CRM token. Log back in to this org by clicking on your username." The help bubble beside this warning states that this impacts scheduled jobs from running in all of your CRM environments. Have I understood this correctly? We have a bunch of scheduled jobs in the production CRM that haven't been running because we didn't log into DemandTools and notice this error. My question is why does the log in for the sandbox environment impact the behaviour of the production environment? We want to be able to rely on these scheduled jobs doing what they need to be doing in the background at all times.
Hey @Asti - So the only requirements for scheduled jobs to operate as expected are that the machine is on and connected to the internet. While you need to have logged into DemandTools at one point to have the job running, you shouldn't need to have it open to have the job run. If you are experiencing something that does not align up with those requirements, please reach out to our support team (support@validity.com) to discuss further. Thanks!
Hey @Pugs_Validity thank you for your reply! I'll reach out to your support team in that case, I can then provide a screenshot of the error that might help. I understand that I don't need to have DemandTools open to run my scheduled jobs. My question is why being logged out of the sandbox environment in DT (but still logged into the Prod environment) impacted the running of the scheduled jobs I had in the Prod environment.
