PhantomBuster "Fail to follow" / "You've been rate limited" errors are platform blocks, not PhantomBuster bugs

PhantomBuster "Fail to follow" / "You've been rate limited" errors are platform blocks, not PhantomBuster bugs

TL;DR

When logs show platform limit messages, the Phantom is configured fine; the platform is throttling you: Operational rules from the docs: reduce the number of actions per launch, space out launches, never run multiple high-activity Phantoms at once, and wait before relaunching during an active restriction. Repeated relaunches during a block can extend the block duration.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

PhantomBuster - Official docs (support.phantombuster.com): PhantomBuster's platform-limits guide documents that errors like "Fail to follow", "You've been rate limited by [platform], please retry later", "Couldn't click on Unfollow button", "Unable to find DM button", and "Rate limit reached, waiting 30.0s" come from the external platform (Instagram, X/Twitter, Slack) temporarily restricting actions, not from a broken Phantom.

The fix

• "Fail to follow" / "Couldn't click on Unfollow button" (Instagram): temporary action block from too many actions. Wait it out, reduce actions per launch.
• "You've been rate limited by [platform], please retry later" (Instagram/X): platform-side restriction. Space out launches, don't run back-to-back.
• "Unable to find DM button" (X/Twitter): that profile's DM restrictions, not a bug. Skip those profiles.
• "Rate limit reached, waiting 30.0s" (Slack): Slack delaying API responses. The Phantom is still running and waiting; let it finish, don't kill and relaunch.

Use the exact log message to match their error table and open the linked article for that message.

Thread: docs:phantombuster:platform-limits-errors

In docs:phantombuster:platform-limits-errors (https://support.phantombuster.com/hc/en-us/articles/33374398344338-Overview-of-Platform-Limits-Restrictions-Errors-Instagram-X-Twitter-Slack), the issue reported: Official docs (support.phantombuster.com): PhantomBuster's platform-limits guide documents that errors like "Fail to follow", "You've been rate limited by [platform], please retry later", "Couldn't click on Unfollow button", "Unable to find DM button", and "Rate limit reached, waiting 30.0s" come from the external platform (Instagram, X/Twitter, Slack) temporarily restricting actions, not from a broken Phantom. The Phantom starts normally and fails on specific actions. Triggers: too many actions in a short period, API rate limits, DM restrictions, temporary action blocks, platform instability. The verified answer: When logs show platform limit messages, the Phantom is configured fine; the platform is throttling you:

• "Fail to follow" / "Couldn't click on Unfollow button" (Instagram): temporary action block from too many actions. Wait it out, reduce actions per launch.
• "You've been rate limited by [platform], please retry later" (Instagram/X): platform-side restriction. Space out launches, don't run back-to-back.
• "Unable to find DM button" (X/Twitter): that profile's DM restrictions, not a bug. Skip those profiles.
• "Rate limit reached, waiting 30.0s" (Slack): Slack delaying API responses. The Phantom is still running and waiting; let it finish, don't kill and relaunch.

Operational rules from the docs: reduce the number of actions per launch, space out launches, never run multiple high-activity Phantoms at once, and wait before relaunching during an active restriction. Repeated relaunches during a block can extend the block duration. Use the exact log message to match their error table and open the linked article for that message.