Mass Unfollow for X Troubleshooting: The Two Checklists the Site Gives and the Order That Uses Both
What the troubleshooting page fixes, what the FAQ checklist adds, and which layer to check first when the button stays dead
Image: Twitter headquarters in San Francisco (TK2) by Tobias Kleinlercher / Wikipedia, licensed under CC BY-SA 3.0.
The troubleshooting page and the FAQ answer the same dead-button complaint with lists that overlap but do not match, and the daily limit that one vendor page says paid plans remove is printed as 500 or 1,000 a day on the store listing. This article sets out both lists, an order that uses them, and the layers neither checklist names.
The first entry on the troubleshooting page is a button that does nothing, and the fix it gives runs to four steps: be on x.com rather than twitter.com, be on your Following list, refresh the page, then reopen the extension popup or disable and re-enable the extension.
The FAQ answers the same complaint with five steps. It keeps the two page conditions and gives the Following list's address as x.com/your-handle/following, adds a check that the license key is entered correctly and a check that the daily limit has not been reached, and ends with the disable-and-re-enable step plus a request to contact support with the license key.
The two lists agree on the page conditions and the extension restart. Each leaves out a layer the other checks: the troubleshooting page says nothing about the license key, and the FAQ says nothing about reopening the popup. Both are short enough to run before changing anything, but neither one says which layer to check first when the button stays dead, and that choice decides how long a stalled session lasts.
The four fixes the troubleshooting page gives
A button that does nothing. The page names the two page conditions first, x.com rather than twitter.com and the Following list. It then gives a refresh, a popup reopen, and, if needed, a disable and re-enable of the extension.
A loading state after payment. The page asks the reader to wait up to 30 seconds while the license is issued, then refresh the success page. If the loading state persists, it points to the dashboard and the license key held there.
A daily limit message. The page states that free plans are limited to 100 unfollows a day and gives two ways out: upgrade to Monthly or Yearly to remove the daily limit, or wait until the next day.
Advanced filters that are not available. The page states that the filters require a paid plan, and directs the reader to the dashboard to upgrade and then to reopen the extension.
A fifth entry covers everything else. The page asks for the license key, the browser version and a quick description of the issue, and the support page says the team replies within 24 hours.
Why the page conditions come first
The extension acts on the page it runs in. Chrome's content-script documentation describes content scripts as files that run in the context of web pages, declared for a set of pages by match pattern, and able to read and change what those pages hold. A tab on twitter.com is a different host from x.com, and a tab on the home timeline is a different page from the Following list. The first two steps put the extension on the page that holds the list it has to work through.
The FAQ list runs in a similar direction. Its five steps move from page state to license state to plan state to extension state, and the order below keeps that progression.
The two layers the FAQ adds
The license key. Every plan requires an account for license management, and the homepage ends its setup steps with entering the license key. A key that was never entered, or entered with a typo, leaves a dead button on a correctly loaded page, and the FAQ's third step checks for it.
The daily limit. The FAQ asks the reader to verify that the limit has not been reached and names the free plan's 100 unfollows a day. The extension reports the cap in its own message, and the troubleshooting page lists that message as a separate entry rather than as part of the button fix.
A separate FAQ answer covers device activations: it lists one device on the free plan, three on Monthly and five on Yearly, and states that each entry of the license key on a new browser or computer counts as an activation, with support able to reset them. Neither checklist names device activations, and a reader who has moved to a second machine will not find them in either one.
An order that uses both lists
The order below follows the two vendor lists and puts the checks that produce a definite answer first.
- Page state. Open x.com rather than twitter.com, go to the Following list, and refresh.
- License key. Open the dashboard and compare the key there with the key entered in the extension.
- Plan cap. Check whether the day's removals have reached the plan's limit before reading the dead button as a fault.
- Extension state. Reopen the popup, then disable and re-enable the extension.
- Support. Send the license key, the browser version and a description of what happened.
The first two steps follow the order both lists use. A reader who reaches the fifth has the three items the troubleshooting page asks for, and the reply window the support page states.
The daily-limit fix and two vendor statements
The troubleshooting page tells a reader who has hit the cap to upgrade, on the stated basis that upgrading to Monthly or Yearly removes the daily limit. The pricing page, read on October 19, 2026, lists the Monthly plan at $4.99 a month and the Yearly plan at $36 a year, describes both as including unlimited unfollows, and answers its cap question by saying that Monthly and yearly plans remove the daily limit.
The Chrome Web Store listing, read the same day, prints a different set: 100 a day on Free, 500 a day on Monthly and 1,000 a day on Yearly. Neither page refers to the other, and no vendor passage reconciles the two statements.
A reader who upgrades to clear the message gets a higher printed cap on the store listing and an unlimited label on the pricing page. The site's own limits guide states that no universal public safe number exists for every account and that an exact daily number found online should be treated with caution, so the 100 in the message is a plan limit rather than a measured safety figure.
The license that arrives after payment
The payment and the license are separate events, which is what the loading-state entry describes: the license is issued after the payment, and the page's first instruction is to wait up to 30 seconds before refreshing the success page. The FAQ describes the upgrade path through the dashboard, states that the license is upgraded immediately, and says a confirmation email follows. If the success page still shows a loading state after the refresh, the dashboard holds the key the reader needs.
What the fixes do not cover
The site's troubleshooting material covers the product's own states: page, license, plan and extension. The X Developer Policy covers a different layer. It is written for developers who work with the X API and X Content, and it directs services that perform write actions, naming following, to follow the Automation Rules and rules out bulk, aggressive or spammy actions, with bulk following given as the example. It sets no numeric threshold, and it says nothing about a browser extension that acts on the site itself.
The Automation Rules page that the policy links to answered a security check when this article tried to read it, so no line from it is quoted here. On the vendor's side, none of the pages read for this article measures whether pacing or filtering changes how X enforces its rules, and the homepage recommends starting conservative without offering a number.
Before sending the email
A reader whose button does nothing can run the page conditions, then the license check, then the cap check, and reach support with the license key, the browser version and a description of what happened. The license check costs the time it takes to open the dashboard. If the cap is the cause, the decision is whether to wait for the next day or to pay, and the paid numbers sit on two pages that do not agree.