This guide explains why session cookies expire and provides clear steps to prevent and fix cookie expiration errors that can stop your PhantomBuster automations.
What is a session cookie error
When a session cookie becomes invalid, your Phantom will display an "Expired session cookie" or "Invalid session cookie" error message.
This prevents PhantomBuster from accessing your account and running your automations.
Several factors can cause your session cookie to expire or become invalid. Let's walk through them below.
Why do session cookies expire or become invalid
Here’s what can cause your session cookie to expire or become invalid:
1. Logged out or session expiration errors
-
Manually logging out of your account ends the session and invalidates the cookie.
-
You may also be logged out automatically after a period of inactivity.
To prevent this: Stay logged into your social media accounts while PhantomBuster automations are running.
2. Exceeding platform rate limits
-
Platforms like LinkedIn, Facebook, and Instagram monitor user activities closely.
-
Sending too many connection requests, messages, or interactions in a short period can trigger warnings, restrictions, or security actions.
-
When this happens, your session cookie may expire or become invalid as a protective measure.
For example, on LinkedIn, some of the most common reasons users receive warnings or temporary account restrictions include:
- Using automation tools
- Exceeding account limitations
- Having too many pending connection requests
- Having too many people mark you as someone they don't know
- Breaking other LinkedIn policies around content, identity, and profiles
For a detailed guide, check out our blog post: LinkedIn Account Restricted? Here's How to Fix It.
How to stay compliant while automating on social media
Social media platforms can easily detect unusual behavior based on how quickly your activity increases and how other users respond to your actions.
For example, sending 5 connection requests one day and 500 the next on LinkedIn is highly suspicious and could lead to warnings or account restrictions.
To prevent this:
- Slowly build up your account activity to mimic natural human behavior.
- Gradually increase the number of actions (messages, requests, likes) over days and weeks.
- When setting up Phantoms and Flows, carefully adjust the Behavior settings to stay within recommended rate limits and avoid sudden spikes.
Adopting realistic behavior patterns greatly reduces the risk of triggering platform security systems, keeping both your session cookie and your account safe.
3. Multiple login locations or devices
-
Social media platforms track where and how you log into your accounts as part of their security measures.
-
Logging into the same account from different devices, IP addresses, or countries at the same time can trigger alerts.
-
For example, if you log manually into Facebook from France while a Phantom accesses it from the USA, Facebook may flag this as suspicious activity and expire your session.
Why this happens
Platforms enforce strict security policies to prevent fraud and spam.
Because you can physically only be in one place at a time, simultaneous logins from different locations are treated as a risk.
To prevent this:
- Use the same device and IP location whenever possible.
- If you need to automate from different regions, set up proxies to manage sessions without conflict.
- Regularly refresh your session cookies by logging into your account.
This helps maintain a stable session and prevents unexpected cookie expiration during automation.
4. Server-side session cookie expiration
-
Some platforms automatically expire session cookies after a set period, even if you remain active.
-
This can cause session cookies to expire without user action.
To prevent this: Regularly log back into your account to refresh your session and ensure your cookie stays active.
How to Fix "Expired Session Cookie" or "Invalid Session Cookie" Errors
If your Phantom shows a session cookie error during execution:
Example of an "Expired session cookie" error displayed in a Phantom's console.
Follow these steps to refresh your session:
1. Go to your PhantomBuster Dashboard.
2. Find the Phantom that triggered the error.
➔ It will display a warning icon where your platform identity usually appears, along with an error tag.
3. Click on the error displayed on the Phantom card.
➔ This will open the Phantom's console, where you can view the error message.
4. Click the Resolve button inside the console.
5. You will be redirected to the Phantom’s Setup page.
➔ Click the Connect now button to reconnect to the platform.
6. The browser extension will automatically detect your new session.
➔ Click Save to confirm the new connection.
Your session cookie has been refreshed and your Phantom can now run normally.
How to avoid future session Cookie errors
To reduce the risk of session cookie expiration or invalidation:
-
Stay logged into your platform accounts while running PhantomBuster automations.
-
Gradually scale your activity to stay within platform-imposed limits.
-
Use consistent devices and IP addresses, or set up proxies when needed.
-
Regularly refresh your session by logging into your account.