Official documentation checked October 14, 2026.
A Perplexity shared conversation that displays “Not Found” needs an access and existence check. The message alone does not prove that a link expired. Preserve the complete URL and ask the owner to verify the original session before changing sharing settings.
Current help uses “session” for the conversations older guides call threads. This guide covers that object, rather than assuming that a Project invitation or another shared artifact uses the same access rules.
Check the Link, the Session and the Intended Audience
Possible checks include a truncated URL, an incorrect account, changed visibility, removal of the session and service trouble. Treat each as a possibility to investigate, not a diagnosis established by the wording of an error page.
The official session guide documents private access, anyone-with-the-link access and an organization-scoped option. It does not establish the earlier article’s seven-day/30-day share-link defaults, ten-link cap or an Expires date picker.
Separately, official access troubleshooting explains that sessions created while signed out disappear after fourteen days. That is a limit on anonymous sessions, not a universal expiration policy for links shared from signed-in accounts.
Follow the Appropriate Viewer or Owner Checks
If you received the link
- Copy the complete original URL again from the sender’s message. Check for truncation or punctuation accidentally added outside the link; do not guess or rewrite its identifier.
- Ask the owner whether the original conversation still opens and whether you are in its intended audience.
- For an organization-restricted link, use the authorized account and organization. A signed-out test will not validate access intended only for members.
- If it is deliberately public, compare the exact link in another browser context to distinguish author-only access from public access.
If you own the session
- Open the correct account and find the session in History. Keep any working copy open.
- Inspect its Share panel and current audience. Recopy the link through the available sharing control.
- Change the audience only if that is the intended sharing decision. Review the whole conversation before allowing anyone with the link to read it.
- Have an intended recipient test the copied URL. Note the account context and result.
Do not publish a private conversation merely to make an error disappear. A copied private URL does not give the recipient permission.
Handle Missing Sessions and Projects Separately
If the owner cannot find the conversation, compare the exact account email and sign-in method. The access guide notes account mismatches, including Apple relay addresses. Check saved links or your own browser history before clearing browsing data.
The session guide says deleted sessions cannot be recovered. Do not delete and recreate a surviving session as a repair experiment. A newly generated conversation would be new work with potentially different answers and sources.
Projects have their own membership and sharing rules. Check the object being shared and the recipient’s actual access. Inviting someone to a Project is a separate permission decision; do not move private material to a public destination to bypass that check.
Escalate an Unexplained Failure with Useful Evidence
| Check | Record |
|---|---|
| Owner access | Whether the original session opens |
| Sharing scope | The audience displayed by the Share panel |
| Recipient test | Intended account context, time and exact message |
| Client comparison | Whether another supported browser/client behaves differently |
If the original exists and access appears correct, use Help > Contact Support with the session URL and redacted reproduction details. There is no verified universal “Never expires” switch or subscription upgrade that fixes this condition. Keep important permitted material in a checked backup; a share link alone is not a backup.
Glad it helped. Take a short break with a game:
Sorry about that. Search for the exact error message, or look for a tool that checks your device: