How to Stop Phantoms from Running

This guide explains how to stop a Phantom or Workflow from running, how to unschedule future launches, and why LinkedIn messages may still be sent even after a Phantom has been deleted.

Stop a Phantom that is currently running

If a Phantom is running right now, you can stop it immediately:

  1. Go to your Dashboard.
  2. Locate your Phantom and click on it to access the console page.
  3. Click the Stop button to halt the execution.

This will only stop the current run. If the Phantom is scheduled to run again later, it will continue to do so unless you unschedule it.

phantom-console-stop-button.jpeg

Unschedule a Phantom to stop automatic launches

To stop a Phantom from launching automatically in the future:

  1. Go to your Dashboard.
  2. Locate the Phantom.
  3. Click the toggle below the Phantom’s name to unschedule it.

This disables the Phantom’s recurring schedule but keeps the Phantom available for manual runs.

dashboard-deactivate-toggle-scheduled-launch.jpeg

Stop a Flow

If the Phantom is part of a multi-step flow:

  1. Go to your Dashboard.
  2. Locate the Flow.
  3. Click the toggle below the Flow name to switch it off.

This will pause the entire Flow and prevent all connected Phantoms from running again until the Flow is re-enabled.

dashboard-deactivate-flow-toggle.jpeg

Why LinkedIn messages may still be sending

If you used the LinkedIn Auto Connect Phantom with a message and are still seeing messages go out after stopping or deleting the Phantom, this is expected behavior.

LinkedIn only sends your message when the recipient accepts the connection request, not when the request was originally sent.

This means:

  • The Phantom is not running again.
  • You're seeing delayed messages from earlier connection requests.
  • Messages can be triggered days or even weeks later, depending on when people accept.

Example:
You used the Phantom two weeks ago. A user accepts your request today. The message you attached will send now, even though the Phantom hasn’t run recently.

This behavior is controlled by LinkedIn and cannot be stopped from PhantomBuster once the request is sent.

Related guides 

 

 

Was this article helpful?

0 out of 0 found this helpful