This guide explains what system and execution errors mean, which Phantoms they typically affect, and how to identify the correct troubleshooting steps.
What triggers these errors
System and execution errors occur while the Phantom is actively running.
They are triggered when:
- A run exceeds the maximum runtime limit.
- Too many executions run in parallel.
- The Phantom runs out of memory.
- The execution environment is interrupted.
When this happens, you may notice:
- The run stops mid-execution.
- Partial results are saved.
- Logs reference runtime, memory, or parallel limits.
These errors are related to how the Phantom runs, not how it was configured.
Common system & execution errors
The table below maps common runtime messages to their corresponding troubleshooting guides.
| Error message shown in logs | What it means | Phantoms typically impacted | Troubleshooting guide |
|---|---|---|---|
| Maximum run time has been reached | The run exceeded the 5-hour execution limit | Data extraction Phantoms, large input jobs | How to Fix the “Maximum Run Time Has Been Reached” Error |
| Maximum number of parallel executions reached | Too many automations running at the same time. This may happen if several Phantoms are scheduled together or if external tools (like n8n, Make, or API scripts) trigger multiple launches simultaneously. | Any Phantom or Workflow | How to Fix the “Maximum number of parallel executions reached” Error |
| Waiting time for new logs reached | The Phantom waited too long for platform response and stopped | LinkedIn extraction Phantoms, large input runs | How to Fix the “Waiting time for new logs reached” Error |
| Process terminated with SIGKILL | The Phantom ran out of memory and was force-stopped | Large input Phantoms, heavy extraction tasks | How to Fix the “Process Terminated with SIGKILL” Error |
| Execution context was destroyed | The browser session was interrupted during navigation | Phantoms interacting with dynamic web pages | How to Fix the “Execution context was destroyed” Error |
| [404] Agent not found | The API request references an invalid Phantom ID | API-triggered Phantoms (Make, Zapier, n8n) | How to Fix the “[404] Agent not found” Error |
| There’s nothing to see here yet | The Phantom is still running and results are not ready | Any Phantom during active execution | What the “There’s nothing to see here yet” Message Means |
Operational next steps
If you encounter a system or execution error:
- Reduce the number of rows or items processed per launch.
- Split large input files into smaller batches.
- Space out scheduled launches.
- Avoid running too many Phantoms simultaneously.
- Duplicate a Phantom for clean reprocessing instead of relaunching the same overloaded one.
For Workflows
- Avoid modifying input mid-run.
- If retrying failed leads, use a new input file.
- Create a new Workflow instead of editing an active one.
This helps prevent repeated runtime failures and unnecessary execution time consumption.
How to resolve them
Use the exact error message shown in your logs and match it to the table above.
Open the linked troubleshooting article for detailed, step-by-step instructions tailored to that message. Additional system-related troubleshooting guides are available in this section.
If you’re unsure how to locate or read the error message:
- Read How to Troubleshoot Phantoms Using Logs
- Or How to Troubleshoot Errors in Workflows if you’re using a Workflow.