When a Phantom stops or produces unexpected results, check the console for error messages. Focus on the first error in the logs, that's usually the root cause. Errors fall into six categories: setup or data input issues, connection or authentication problems, platform limits, system or execution limits, credit or storage limits, and integration or API errors. Use this guide to identify which category your error falls into and navigate to the right troubleshooting section.
Understand the type of message you're seeing
When you open a Phantom's console, you may see different types of messages:
- Error: The Phantom stopped. Action is required.
- Warning: The Phantom completed, but part of the execution failed.
- Info: Informational message. No action is needed unless results are missing.
If your Phantom stopped completely, always focus on the first error shown in the execution logs. That's usually the root cause. Errors later in the log are often consequences of the first one.
If you're unsure how to read the logs or locate the error message:
- Read How to Troubleshoot Phantoms Using Logs for a step-by-step explanation.
- Read How to Troubleshoot Errors in Workflows if the issue occurs in a Workflow.
Once you understand what the error refers to, use the categories below to find the appropriate troubleshooting section.
Setup or data input errors
The Phantom can't use the data you provided.
This may happen if:
- A required field is empty.
- A URL isn't valid.
- A spreadsheet column is incorrectly formatted.
- You see 'Could not validate data' when creating a Workspace.
Go to the Fix Setup & Data Input Errors section to review common error messages, understand how they behave, and access related troubleshooting guides.
Connection or authentication errors
The Phantom can't access your connected account.
This may happen if:
- Your session cookie expired or is invalid.
- Your account was disconnected.
- A proxy is misconfigured.
- The platform requires manual confirmation (e.g., Instagram Terms update).
Go to the Fix Connection & Authentication Errors section to review common error messages, understand how they behave, and access related troubleshooting guides.
Platform limits or restrictions
The social platform blocked or limited the action.
This may happen if:
- You reached LinkedIn invitation limits.
- You have no InMail credits left.
- A search limit was reached.
- A profile is out of network.
- Instagram or X/Twitter restricts certain actions.
Go to the Fix Platform Limits section to review common error messages, understand how they behave, and access related troubleshooting guides.
System or execution limits
The Phantom stopped due to runtime or system constraints.
This may happen if:
- Maximum run time was reached.
- Too many executions are running at once.
- A technical runtime error occurred.
- The execution context was destroyed.
Go to Fix System & Execution Errors section to review common error messages, understand how they behave, and access related troubleshooting guides.
Credit or storage limits
Your Workspace has reached a resource limit.
This may happen if:
- Storage is full.
- Lead capacity is reached.
- AI credits are exhausted.
- Email discovery credits are used up.
Go to Fix Credit & Storage Errors section to review common error messages, understand how they behave, and access related troubleshooting guides.
Integration or API errors
A connected tool or external service failed.
This may happen if:
- An API key is invalid.
- A wrong endpoint was used.
- The API request is incorrectly built and never reaches PhantomBuster.
- A CRM didn't update.
- Email discovery is temporarily unavailable.
- An automation tool like n8n triggered incorrectly.
In some API cases, the request may not reach our server at all (for example, if the API key or endpoint is incorrect).
If you suspect an API configuration issue and don't see logs on our side:
- Record a short video of your setup.
- Show the exact request configuration and the moment of failure.
- Share it with our team.
Go to the Fix Integration & API Errors section to review common error messages, understand how they behave, and access related troubleshooting guides.
When to contact our Customer Care Team
- If you've identified the category and followed the related troubleshooting steps but the issue persists, the problem may require deeper investigation from our team.
- Before contacting support, review How to Record a Bug for PhantomBuster's Customer Care Team to make sure you include the right details.
Frequently asked questions
What is the difference between an error, a warning, and an info message?
An error means the Phantom stopped and action is required. A warning means the Phantom completed but part of the execution failed. An info message is informational and typically requires no action unless results are missing.
Which error message should I focus on first?
Always focus on the first error shown in the execution logs. That is usually the root cause. Later errors are often consequences of the first one.
Where can I find my Phantom's error logs?
Open the Phantom's console page in your PhantomBuster Workspace. The execution logs show all messages from the most recent run. See How to Troubleshoot Phantoms Using Logs for a step-by-step walkthrough.
What should I do if none of the troubleshooting steps fix my error?
Review How to Record a Bug for PhantomBuster's Customer Care Team to gather the right details, then contact support for deeper investigation.