How to Troubleshoot Errors in Workflows

To troubleshoot a Workflow, open its console page (replace "dashboard" with "console" in the URL, or enable Developer mode for a permanent button), then go to the Activity tab and click View log. Check the main Workflow log for the overall status, and open individual worker agent logs to see what happened at each step. If a specific step failed, click on that worker agent from the Activity tab to find the exact error message.

→ If you're using an individual Phantom, check out How to Troubleshoot Phantoms Using Logs instead.

Workflows covered in this guide

This troubleshooting process applies to all current Workflows in PhantomBuster.

Review logs for insights

The first step in troubleshooting is to check your logs.

Logs record everything your Workflow did during a run, step by step.
They help you pinpoint where something went wrong, whether it's an issue with the overall Workflow or a specific step.

Each Workflow includes two kinds of logs:

The main Workflow log → tracks the overall progress and completion status.
The worker agent logs → show what happened within each Phantom that makes up the Workflow.

How to access logs

From your Workflow's Dashboard, you can open the console page to review detailed execution logs and error messages.
There are two ways to access it, depending on your settings:

Option 1 – Using the address bar

Go to your PhantomBuster Dashboard, and click on the Workflow you want to review.
In your browser's address bar, replace the word "dashboard" with "console" and press Enter.
→ This opens the Workflow's console page.
Open the Activity tab.
Find the run you want to check, hover over it and click View log.
Read at the Output box to see whether the Workflow completed normally, stopped early, or encountered an error.

Option 2 – Using Developer mode (adds a permanent console button)

Go to your User menu › My space › My personal settings.
Check the box Enable developer mode.
Go to your PhantomBuster Dashboard and click the Workflow to open its Dashboard.
In the top-right corner, click the three dots menu.

With Developer mode enabled, you'll also see extra options:
- Agent object – view the Workflow's underlying JSON data.
- API – generate ready-to-use API call snippets.
Select Switch to console.

How Workflow interfaces differ

Some Workflows open directly on the console view (Results and Activity tabs) rather than showing a Dashboard.
In these cases, you can access logs immediately, there's no need to switch views.

→ Workflows that include a Dashboard (with Leads and Report tabs) are listed in Track outreach performance in Workflows.

What to look for in the logs

When reviewing logs, focus on:

Error messages: Short notes that explain why something failed.
Incomplete actions: Signs the Workflow stopped before finishing (for example, it ran out of execution time).
Delays between steps: pauses that can explain slowdowns or timing issues.

Checking logs for each Workflow step

If one specific step isn't working (for example, invitations aren't being sent), you can open that step's individual log:

On the Workflow's console page, open the Activity tab.
On the right-hand side, locate the list of worker agents (the Phantoms inside your Workflow).
Click the one you want to check to open its console page.
Hover over the relevant launch and click View log.
Check the Output box for any errors or status updates.

Example:
→ If the invitation step fails, open the LinkedIn Auto Connect worker agent's log to see what caused it.

Common issues and fixes

Profiles with errors not being reprocessed

Once a lead or profile has been processed, it won't be reprocessed automatically. To retry errored profiles:

Download the CSV results file from the Workflow's console page.
Copy the errored profiles into a new Google Sheet.
Make sure sharing access is set to Anyone with the link can view.
Create a new Workflow and use the Google Sheet URL as the input file to reprocess those profiles.

Workflow launched, but no visible activity

It's normal for some Workflows to take a few minutes before visible actions start.

When launched, Workflows run steps in sequence (e.g. extracting profiles → sending invites).
This design ensures safe and orderly execution.

→ Wait until the Workflow completes early steps like profile extraction before expecting invitations or messages to appear.

Changing input after launch

Changing the input mid-run can disrupt the Workflow.

If you need to update the input:

If your input is a single URL: Start a new Workflow to process the new URL.
If your input is a spreadsheet: You can safely add new rows of the same type.
→ The Workflow will automatically pick them up (e.g., if the input is LinkedIn search URLs, the new entries must also be LinkedIn search URLs).

Frequently asked questions

How do I access the console for a Workflow?

Open the Workflow from your Dashboard, then replace "dashboard" with "console" in your browser's address bar and press Enter. Alternatively, enable Developer mode in My personal settings, then use the three-dot menu and select Switch to console.

What is the difference between the main Workflow log and worker agent logs?

The main Workflow log tracks overall progress and completion status. Worker agent logs show what happened within each individual Phantom that makes up the Workflow. If a specific step failed, open that worker agent's log to find the error.

Why does my Workflow show no activity after launching?

Workflows run steps in sequence. For example, extracting profiles before sending invitations. It's normal for the first visible actions to take a few minutes. Wait until the Workflow completes its early steps before expecting later actions to appear.

Can I reprocess profiles that had errors?

Yes. Download the CSV results file from the Workflow's console page, copy the errored profiles into a new Google Sheet with sharing set to "Anyone with the link can view," then create a new Workflow using that sheet as input.

Can I change the input of a running Workflow?

If the input is a single URL, start a new Workflow with the new URL. If the input is a spreadsheet, you can safely add new rows of the same type and the Workflow will pick them up automatically.