Reducing LinkedIn cookie expiry risk with varied launch times

If you’re running LinkedIn Profile Scraper and seeing cookies expire even when staying under daily limits, the issue might be fixed patterns in your launch schedule. LinkedIn can detect repetitive behavior, so spreading runs out unpredictably can help. 

Note: Cookie expiration can also be caused by other factors, such as an account that isn’t sufficiently warmed up, too many actions processed manually, or other Phantoms running at the same time.

A safer approach:
Spread activity out over more, smaller runs at unpredictable times. Instead of 3 dense sessions (e.g., 9:00, 12:00, 3:00), try 6–8 lighter runs across the day with minutes randomized, like 9:15, 11:40, 2:05, 4:30.

Step-by-step with Zapier or Make (since randomization isn’t built into PhantomBuster):
1. Add a schedule trigger in Zapier/Make to run every hour during your chosen working hours.

2. Insert a code step to generate a random delay:
// Generates a random delay between 5 and 30 minutes
const min = 5; 
const max = 30; 
const delayMinutes = Math.floor(Math.random() * (max - min + 1)) + min;

return { delayMinutes };

3. Use a delay module to wait the randomized number of minutes before running the Phantom.

4. Launch your Phantom after the delay.

5. Keep volumes low, especially if the account hasn’t run high activity before.

Following this flow helps avoid suspicious patterns and can reduce the risk of LinkedIn cookie expiry.