Why you shouldn’t alter your LinkedIn session mid-automation

Once you start your Dux-Soup Cloud session in Dux-Dash → Cloud Monitor, it’s critical to avoid making changes to your local LinkedIn session. Doing so can lead to unexpected shutdowns of your cloud session, interrupting your automated workflows.

Why This Happens

Dux-Soup Cloud Monitor operates your LinkedIn account remotely by mimicking a session based on the local credentials and cookies stored at the time of launch. If you:

• Log out of LinkedIn locally,
• Log in from a different browser or device,
• Use VPNs that significantly alter your IP or location,

…you effectively invalidate the cloud session’s authentication. This causes the cloud instance to shut down because it no longer has a valid session to operate under.

Best Practices

To ensure your cloud automation runs smoothly:

• Launch Cloud Monitor only after your local LinkedIn session is stable and authenticated. If you're using Sales Navigator or Recruiter, make sure to complete two-factor authentication (2FA) first.
• Avoid logging out of LinkedIn while Dux-Soup Cloud is running.

By maintaining a consistent LinkedIn session, you ensure uninterrupted automation and avoid errors or activity loss within your Dux-Soup campaigns.