When you click a link to a Perplexity shared thread, you may see a page that says “Not Found” instead of the conversation you expected. This error usually means the thread link has expired, the thread was deleted, or the sharing settings were changed after the link was created. This article explains the three main reasons for the “Not Found” error and gives you step-by-step fixes for each scenario.
Key Takeaways: Fixing a “Not Found” Shared Thread in Perplexity
- Check thread expiration: Shared links with an expiration date show “Not Found” after the date passes
- Verify thread deletion status: The original thread must still exist in the creator’s account for the link to work
- Request a new share link: The thread owner can regenerate a share link from the thread’s menu
Why Perplexity Shared Threads Show “Not Found”
Perplexity shared threads are temporary by default. When you share a thread, Perplexity creates a unique URL that points to a snapshot of that conversation. That snapshot can be set to expire after a certain time, or it can be set to never expire. If the expiration time has passed, the link returns a “Not Found” error.
Another common cause is thread deletion. If the original thread is deleted from the creator’s account, the shared link immediately stops working. Perplexity does not keep a copy of the thread after deletion. The same happens if the creator changes the sharing settings to “Private” after the link was shared.
A less common cause is a typo or truncation in the URL. Shared thread URLs are long and contain a unique alphanumeric ID. If a user copies only part of the URL, or if the link is broken in an email or chat message, the page cannot find the thread and shows “Not Found”.
Steps to Fix the “Not Found” Error on a Shared Thread
The fix depends on whether you are the thread creator or someone trying to view a shared thread. Follow the set of steps that matches your situation.
If You Are the Person Trying to View the Thread
- Check the URL for typos
Look at the address bar. Make sure the URL starts withhttps://www.perplexity.ai/search/and contains a long string of letters and numbers after that. If the URL ends with a period or has extra spaces, remove them and try again. - Ask the sender to confirm the link is still active
Send a message to the person who shared the link. Ask them to open their Perplexity account, find the thread, and check if the share toggle is still set to “Public” or “Anyone with the link”. If they changed it to “Private”, the link will stop working. - Ask the sender to check the thread’s expiration date
If the thread was shared with an expiration date, the link will stop working after that date. The sender can see the expiration date by clicking the share icon on the thread and looking at the “Expires” field. They may need to create a new share link. - Request a new share link
If the original link is expired or the settings changed, the sender can generate a fresh link. Tell them to open the thread, click the Share button, set the expiration to “Never” or a future date, and copy the new URL.
If You Are the Thread Creator
- Log in to your Perplexity account
Open Perplexity and sign in with the account you used to create the thread. - Locate the shared thread
Go to your Library and find the thread. If you have many threads, use the search bar to find it by title or a keyword from the conversation. - Open the sharing settings
Click the Share icon (it looks like a paper airplane or a link icon) next to the thread title. A sharing dialog box opens. - Check the visibility setting
Make sure the toggle is set to “Anyone with the link” or “Public”. If it is set to “Private”, the shared link will show “Not Found”. Switch it to the desired public setting. - Check the expiration date
In the same dialog, look for an “Expires” dropdown or date picker. If the date has already passed, change it to “Never” or a future date. Perplexity will update the existing link automatically. - Copy the link again
After changing the settings, click “Copy link” to get the updated URL. Send this new link to the person who reported the error.
If the Shared Thread Still Shows “Not Found” After the Main Fix
The thread was deleted and cannot be recovered
If you deleted the thread from your Library, the shared link is permanently broken. Perplexity does not offer a trash or recycle bin for threads. You must recreate the conversation from scratch. To prevent this in the future, avoid deleting threads that you have shared with others. Instead, keep them in your Library with the share setting active.
The shared link was generated by a different account
If you have multiple Perplexity accounts, you may have shared the thread from one account but are now logged into another. Log out and log in with the account that originally created the thread. Then check the sharing settings and expiration date as described above.
The link was shared inside a private workspace
Perplexity allows you to create workspaces for teams. If the thread was shared from a workspace, only members of that workspace can view it. If you are not a member, the link will show “Not Found”. Ask the workspace owner to add you as a member or to share the thread from a public workspace instead.
Perplexity Free vs Pro: Shared Thread Expiration Defaults
| Item | Free Plan | Pro Plan |
|---|---|---|
| Default expiration for new shared threads | 7 days | 30 days |
| Option to set expiration to “Never” | Yes | Yes |
| Maximum number of active shared threads | 10 | Unlimited |
| Ability to change expiration after sharing | Yes | Yes |
The table shows that both plans let you change the expiration setting after sharing. If you share threads frequently, set the expiration to “Never” to avoid “Not Found” errors for your viewers.
To recap, the “Not Found” error on a Perplexity shared thread is caused by expiration, deletion, or a broken URL. If you are the viewer, ask the sender to check the sharing settings and regenerate the link. If you are the creator, log in, open the thread, and update the visibility or expiration in the Share dialog. Always set the expiration to “Never” for threads you plan to share long-term. This small change prevents the error from happening again.