You ask a question in Perplexity, get a good answer, then type a follow-up. Instead of a new response, you see nothing or an error message. This usually happens because of a temporary server glitch, a browser cache conflict, or a session timeout. This article explains the root causes and provides step-by-step fixes to get your follow-up questions working again.
Key Takeaways: Fixing Follow-Up Question Generation in Perplexity
- Ctrl + F5 (Hard Reload): Clears the page cache and forces Perplexity to reload the thread engine.
- Settings > Account > Sign Out and Sign In: Resets your session token, which often resolves silent generation failures.
- Disable ad-blockers or script blockers: These extensions can block Perplexity’s dynamic content loading for follow-up requests.
Why Perplexity Stops Generating Follow-Up Questions
Perplexity uses a continuous thread system. When you ask a follow-up, the app sends a request to the server along with the full conversation history. If any part of this chain breaks, the server returns nothing or an error. Common causes include:
- Session token expired: The authentication token stored in your browser or app session has timed out. Perplexity cannot verify your identity for the follow-up request.
- API rate limit reached: Free accounts have a limit of 5 Pro searches per day. After that, follow-ups may silently fail instead of showing a clear warning.
- Browser cache conflict: Stale JavaScript files or cached HTML from a previous session prevent the follow-up input from binding to the response handler.
- Ad-blocker or script blocker interference: Extensions like uBlock Origin or NoScript can block the dynamic script that loads the follow-up generation function.
- Server-side glitch: Perplexity’s backend occasionally drops connections during high traffic. The request is sent but no response comes back.
Understanding these causes helps you choose the right fix. The steps below address each root cause in order of likelihood.
Steps to Fix Follow-Up Question Generation
Follow these steps in the order listed. Test after each step by typing a simple follow-up such as “Tell me more about the second point.”
- Hard reload the page
Press Ctrl + F5 on Windows or Cmd + Shift + R on Mac. This forces the browser to download fresh copies of all page resources. Do not use the regular F5 or refresh button because that may reuse cached files. - Sign out and sign back in
Click your profile icon in the top-right corner of Perplexity. Select Sign Out. Wait 10 seconds. Sign in again with your credentials. This generates a new session token and clears any stale authentication state. - Disable browser extensions temporarily
Open your browser’s extension manager. Disable all ad-blockers, script blockers, and privacy extensions. Reload Perplexity and test the follow-up. If it works, re-enable extensions one by one to find the culprit. - Switch to a different browser or device
Open Perplexity in a browser you rarely use, such as Microsoft Edge if you normally use Chrome, or vice versa. Test the same thread. If the follow-up works on the other browser, the issue is specific to your primary browser’s profile or cache. - Clear browser cache and cookies for Perplexity only
In Chrome, go to Settings > Privacy and Security > Site Settings > All Sites. Search for “perplexity.ai”. Click the trash icon next to the site data. This removes only Perplexity’s cache and cookies without affecting other sites. Reload the page and test. - Check your search allowance
Free accounts get 5 Pro searches per day. Open a new thread and ask a simple question. If Perplexity shows a message about reaching the limit, your follow-up may have failed because of rate limiting. Wait until the next day or upgrade to Pro. - Try incognito or private mode
Open a private browsing window. Sign in to Perplexity. Ask a question and then a follow-up. Private mode bypasses most cache and extension issues. If it works, the problem is in your normal browsing profile. - Update your browser
An outdated browser can have compatibility issues with Perplexity’s dynamic content loading. Check for updates in your browser’s About section. Install any pending updates and restart the browser.
If Perplexity Still Fails to Generate Follow-Ups
If none of the above steps work, the problem likely lies on Perplexity’s side or with your network. Try these additional checks.
Follow-Up Works in a New Thread but Not the Current One
This points to a corrupted thread. Open a new thread by clicking the New Thread button in the sidebar. Paste your original question and ask the follow-up again. If it works, the old thread had a data structure error that prevented new responses.
All Follow-Ups Fail on Every Browser and Device
This suggests a network firewall or corporate proxy is blocking WebSocket connections. Perplexity uses WebSockets for real-time response streaming. Check with your IT department if you are on a corporate network. Try using a mobile hotspot to rule out network restrictions.
Error Message Shows “429 Too Many Requests”
You have hit the API rate limit. Perplexity allows about 50 requests per hour for free accounts. Wait 15 to 30 minutes before trying again. Pro accounts have higher limits. Upgrade to Pro if this occurs frequently.
Error Message Shows “500 Internal Server Error”
This is a server-side error on Perplexity’s end. Wait 10 minutes and try again. You can check Perplexity’s status page at status.perplexity.ai for any ongoing outages.
Perplexity Free vs Pro: Follow-Up Limitations
| Item | Free Account | Pro Account |
|---|---|---|
| Pro search queries per day | 5 | Unlimited |
| API rate limit per hour | ~50 requests | ~500 requests |
| Follow-up generation | Supported, subject to limits | Supported, subject to higher limits |
| Model access | Perplexity default model only | GPT-4, Claude 3, Mistral Large, Perplexity default |
| Priority support | No | Yes |
If you frequently encounter follow-up failures due to rate limits, upgrading to Pro removes the daily search cap and raises the hourly request limit significantly.
You can now resolve the “Follow-Up Question Not Generating” error by performing a hard reload, signing out and back in, disabling conflicting extensions, or clearing site-specific cache. If the problem persists, check your network for WebSocket blocking or use a new thread. For frequent rate-limit issues, consider upgrading to Pro for unlimited searches and higher request thresholds. As an advanced tip, you can use the keyboard shortcut Ctrl + Enter to submit a follow-up without clicking the send button, which sometimes bypasses minor UI rendering bugs.