To troubleshoot a Phantom, open its console page, go to the Activity tab, and click View log on the launch you want to investigate. Focus on the first error message in the log, that's usually the root cause. Logs show the step-by-step execution including authentication, input processing, results retrieved, and any errors or skipped items. If you already know your error message, use the quick links below to jump to the right troubleshooting guide.
→ If you're using a Workflow, check out How to Troubleshoot Errors in Workflows instead.
Looking for a specific error
If you already have an error message from your logs, jump directly to the right troubleshooting guide:
- Setup & input errors (invalid input, Google Sheets access, missing data, argument not valid) → Overview of Setup and Data Input Errors
- LinkedIn & Sales Navigator errors (profile out of network, search limit reached, connection requests not sent, send button missing) → Overview of LinkedIn & Sales Navigator Platform Errors
- Connection & authentication errors (session cookie expired, missing cookie, proxy issues, rate limiting) → Overview of Connection and Authentication Errors
- Platform limit errors — Instagram, X/Twitter, Slack (fail to follow, can't unfollow, DM button not found, rate limit reached) → Overview of Platform Limits & Restrictions Errors
- Integration & API errors (webhook timeout, CRM not updated, n8n multiple triggers, email discovery unavailable) → Overview of Integration and API Errors
- Credit & storage errors (storage full, out of invitations, lead limit reached, export limit) → Overview of Credit and Storage Limit Errors
- System & execution errors (SIGKILL, max run time reached, context destroyed, agent not found) → Overview of System & Execution Errors
Don't know which error type you have? Keep reading to learn how to find and read your error logs.
What to look for in a log
Use these checkpoints to pinpoint issues quickly:
- Error messages: Short codes or descriptions that explain what failed. Match them to the error guides linked above.
- Incomplete actions: Signs the run stopped early. For example, the account ran out of available execution time.
- Input issues: Incorrect link type, empty file, wrong column headers, or access restrictions on a linked spreadsheet.
- Authentication: No confirmation of a successful connection where one is required.
- Delays: Large gaps between actions that may point to blocking pop-ups, limits, or a misconfiguration.
Access and check Phantom logs
Logs are your first stop when a run doesn't go as planned. They show what the Phantom did, step by step.
To access Phantom's launch logs
- Open your Phantom's console page.
- Select the Activity tab to view launch logs.
- Once you access Phantom's activity tab, you'll see a status indicator summarizing the outcome of each launch:
- ✅ Green checkmark: The launch finished successfully.
- ⚠️ Yellow exclamation point: Warnings (e.g., UI blocking, export limits, or URL finder limits). These are cautionary messages, not failures.
- ❌ Red cross: Launch ended with an error and requires troubleshooting (often setup-related).
- ℹ️ Blue info: Informational messages (e.g., "Input already processed").
- Hover over the launch you're interested in and click View log to see the detailed output.
Navigate and understand a log
The log is a summary of what happened during that launch:
- Log ID: A unique identifier for this specific execution.
- Status: Overall outcome (e.g., Success or Error).
- Timestamps: Start, launch, and end times for the run.
-
Process summary: A quick recap of key steps, such as:
- Authentication: Confirms the Phantom successfully connected (e.g., "Connected successfully as [username]").
- Profiles/Items Found: How many results or items were retrieved (e.g., "10 profiles found").
- Log navigation: Move between runs with Older and Newer arrows.
-
Output Section: The human-readable rundown of the run, typically including:
- Input: The query, list or link the Phantom processed.
- Results per search / processed items: Counts of what was handled.
- Successful connection: Confirms login/authentication where relevant.
- Current action: What the Phantom was doing at each moment.
-
Result object: The structured data returned by the run, often including:
- Profiles found / items: Total retrieved.
- Processed data: Contains names, URLs, or other extracted details.
- Errors or skips: Lists any profiles or lines that failed to process.
- Runtime events: Behind-the-scenes technical events for deeper diagnosis (optional to review).
Watch the video tutorial
Frequently asked questions
Where do I find my Phantom's logs?
Open the Phantom's console page and select the Activity tab. Each launch shows a status icon: green for success, yellow for warnings, red for errors, blue for info. Hover over a launch and click View log to see the full details.
What does each status icon mean in the Activity tab?
A green checkmark means the launch finished successfully. A yellow exclamation point indicates warnings but not a failure. A red cross means the launch ended with an error that needs fixing. A blue info icon shows informational messages like "Input already processed."
How do I read a Phantom log?
The log shows the execution step by step: log ID, overall status, timestamps, authentication confirmation, number of items processed, and any errors or skipped items. The output section gives the human-readable summary, while the result object contains the structured data returned.
What should I do if my Phantom shows an error I don't recognize?
Match the error message text to one of the error categories listed at the top of this article, setup, connection, platform limits, system, credit/storage, or integration errors. Each links to a dedicated troubleshooting guide with specific fixes.