The "Waiting time for new logs reached" error appears when your Phantom waits too long for the target platform to load pages or return data and the run times out before finishing. The fix is to reduce the number of inputs per launch, split large input files, and enable automatic relaunches so the Phantom can continue processing across multiple runs.
This error is different from the "Maximum run time has been reached" error, which stops a run that has been going for more than 5 hours. See How to Fix the "Maximum Run Time Has Been Reached" Error if the run completed 5 full hours before stopping.
Why you’re seeing this
This error happens when your Phantom waits too long for the platform to load pages or return data, and the execution times out before finishing.
Common causes include:
- Your input file contains too many rows to process in one run.
- The Phantom is trying to open or interact with too many pages at once.
- The social platform temporarily slows down or delays loading.
- The setup isn’t breaking the task into smaller batches, so the run slows down and eventually times out.
When this happens, your results file may be incomplete because the Phantom stopped before collecting all data.
How to fix it
Reduce the number of inputs per launch
Go to the Behavior step of your Phantom setup and lower the number of rows processed per run. If you're using a Google Sheet, set a smaller number of rows to process for each launch. Running smaller batches (for example, 500–1,000 rows on LinkedIn) helps prevent timeouts.
Enable automatic relaunches
In the Launch Settings step, turn on scheduled or automatic launches. This lets the Phantom continue processing your full list across multiple launches.
Split large input files
If your input file has more than 500 rows, break it into multiple smaller Google Sheets, CSV files, or separate sheets before uploading.
Running in smaller batches keeps the Phantom fast and prevents it from stalling mid-run.
Frequently asked questions
What does "Waiting time for new logs reached" mean?
It means your Phantom waited too long for the target platform to load pages or return data, and the execution timed out before finishing. It's usually caused by processing too many inputs at once or temporary slowness on the platform's side.
How is this different from the "Maximum run time has been reached" error?
The "Maximum run time has been reached" error is triggered when a single launch runs for more than 5 hours. "Waiting time for new logs reached" is triggered earlier, when the Phantom stalls waiting for the platform to respond. Both are fixed by running smaller batches and enabling automatic relaunches.
Will I lose the data already collected when this error appears?
No. Rows processed before the timeout are saved to your results file. When the Phantom relaunches with the same input, it skips already-processed rows and continues from where it stopped.
How many rows should I process per launch to avoid this error?
As a general rule, keep launches under 500–1,000 rows, especially on LinkedIn. If you're still hitting the error, lower the number further and enable automatic relaunches to work through the full list over multiple runs.
Does enabling automatic relaunches resume from where the Phantom stopped?
Yes. When reusing the same input file, PhantomBuster skips already-processed rows automatically, so scheduled or automatic relaunches continue the job without creating duplicates.
If the error keeps showing up
If the error keeps showing up after reducing inputs, splitting your file, and enabling automatic relaunches, get in touch with our Customer Care Team. Please include:
- The Phantom name and a link to the run
- The exact error message from the console
- The size of your input file (number of rows)
- A screenshot of your Behavior and Launch Settings steps