Perplexity Spaces Not Working? Recover Your Research

If Perplexity Spaces is not working or seems missing, check the current Projects section, your signed-in account, and access to the original workspace before recreating anything. Perplexity’s former Spaces help address now leads to its Projects documentation↗ (opens in a new tab). A changed navigation label is different from a page that will not load or a source that cannot be read.

fenbs can keep the reviewed research brief, references, and next steps outside Perplexity, so another assistant can continue from that record. It does not restore a missing Space or automatically copy its sessions and files.

What should you try before starting over?

1. Record the symptom: missing from navigation, denied access, blank page, stalled reply, or an answer that cannot use a source.
2. Save the original link and any accessible, checked findings. Copy unsent text before reloading the page.
3. Confirm the account and organization you normally use. Look under Projects and try the original saved link.
4. Run a small ordinary query, then a small query inside the affected workspace. Compare what fails without adding new files.
5. Test the same link in another current browser or a fresh session. If the failure persists, prepare a support report with the results.

Do not delete sources or create duplicate workspaces just to see whether the page responds. First establish what you can still access. A simple log of these checks makes it easier to identify the next useful action and avoids repeating the same unsuccessful reload.

Is the workspace missing or just in a different place?

The current help describes persistent Projects containing sessions, files, and instructions. Look for the research under the current navigation, then compare its title and source list with your saved record. A similar title is not enough to identify the right workspace if you have several copies.

Try a previously saved project or session link while signed in to the intended account. If it opens, record where it appears in the current layout. If it returns a denial, ask the owner to check the intended audience. If it returns an error, preserve the message instead of assuming the material was deleted.

For a shared project, have its owner confirm that you still have access. The current Projects guidance distinguishes owner, edit, and view access. Do not ask the owner to make private research public as a troubleshooting step; restore the appropriate member access through the available sharing controls.

A separately maintained source index in fenbs helps you identify which research record you are trying to reopen. Keep its approved purpose, owner, and useful references together, rather than relying on a sidebar position that can change.

Does only one page or browser fail?

Compare three things: whether the Perplexity home page responds, whether a normal query completes, and whether the original project link opens. This is a suggested diagnostic sequence, not proof of a particular fault. Write down the result of each comparison before changing the browser setup.

If a fresh session works, inspect the original profile’s site data and extensions with your support team. Save accessible work first, then make one local change at a time. Private browsing may block some sign-in behavior, so a failed private-window test is useful evidence rather than a final diagnosis.

If several devices fail at the same step, check any service notice offered in the app and use the official support route. Avoid unofficial repair extensions or scripts that ask for your session information. A research deadline is a reason to preserve progress, not to give an unknown tool access to private sources.

If your company manages the browser or connection, ask IT before changing its security settings. Record whether the failure occurs on an approved alternate connection when one is available. Do not move company files to a personal account simply to test whether uploads work.

Is the page working but a source unavailable?

A loaded project can still produce an answer that lacks the expected evidence. Check the source itself before rewriting the entire question. Open the original document or webpage with your own authorized account, confirm it is the intended version, and note whether the missing answer depends on text that is actually present.

For files, compare their readiness and location with Perplexity’s file upload guidance↗ (opens in a new tab). Keep persistent project sources distinct from material attached to an individual session. For a size or count refusal, read Perplexity Spaces file limits instead of treating the rejection as a page outage.

• Check the exact filename, document version, and whether the relevant passage can be read in the original.
• Ask one narrow question about one ready source before requesting a broad comparison.
• Open the cited passage and compare it with the answer; a plausible citation label is not a completed verification.
• Record inaccessible or unchecked sources explicitly so the next assistant does not treat them as confirmed evidence.

For example, if a market report’s sales table cannot be retrieved, keep the unanswered table question in the task. Do not replace the missing number with a generated estimate and then describe the research as complete. Continue with other sources only if they genuinely support the needed conclusion.

When should you contact support or change tools?

Use the official Perplexity Help Center↗ (opens in a new tab) and the Help > Contact Support route described in its Projects guidance. Include the safe workspace link, error, time and time zone, browser version, and a short sequence that reproduces the issue. Say what works as well as what fails.

Remove confidential source text from screenshots and never send session cookies or passwords. If a deadline requires another assistant, take only material you are allowed to move and state which evidence has been checked. A new tool still needs access to the original sources; a handoff summary cannot grant it.

For a workspace choice, see Perplexity Spaces vs NotebookLM. Other recovery patterns, such as ChatGPT connectors not working and Copilot instructions not working, cover their own systems. Keep the present investigation focused on Perplexity’s access, page, and source behavior.

How to do this with fenbs

1. Create a free account and add a project for the research question.
2. Add safe source references in Links and listings and concise reviewed findings in AI context notes. Keep original documents in their authorized location.
3. Create tasks for unresolved questions and the access problem. Put the remaining checks in each task’s plan.
4. Connect a supported assistant using the integration guides, ask it to read context, and have it save Where we left off before stopping.

fenbs is free for one person, no credit card. It does not connect to Perplexity or back up its project files. It fits research that needs a durable work record across assistants; if your only problem is restoring a single page, Perplexity support is the appropriate place to resolve it.

Explore the AI at work hub for more research workflows. Once access returns, add the resolution and the next research check to the record so recovery does not quietly become an unsupported claim that the research is finished.