Data loss - threads AND artifacts deleted inside Space (2 separate incidents, unresolved since July 2)

I’m reporting a recurring data loss issue inside a Perplexity Space, distinct from a simple ‘missing thread’ bug — this involves loss of both threads and artifacts (generated files/canvases) within the Space itself.

Incident 1 — Thursday, July 2, 2026: All threads inside my Space disappeared. Artifacts (saved files/documents) remained intact and visible in the Space.

Incident 2 — Monday, July 6, 2026: Same Space lost all threads again, but this time artifacts were also deleted, not just threads. Nothing was manually deleted by me on either occasion. I was logged into my correct account, not in Incognito mode, on both occasions.

I contacted support after Incident 1 (July 2) and received no response. This is now happening for the second time in under a week, with escalating severity (loss extending from threads only to threads + artifacts).

I noted your status page recorded a ‘Computer Sandbox Issue’ incident on July 1, 2026 — this timing correlates directly with my first data loss on July 2. Please confirm whether these incidents are related, and whether recovery of the deleted threads/artifacts from the Space is possible.

Requesting priority escalation given data loss now affects generated artifacts, not just conversation history.

Pre-flight checklist

  • This is about the Perplexity API, not the Perplexity app, Comet, or web UI.
  • I have removed API keys, secrets, and private data.
  • I have included enough information for someone else to reproduce the issue.

Bug type

  • Error response or failed request
  • Incorrect or unexpected model output
  • Missing, invalid, or stale citations/search results
  • Streaming issue
  • Structured output or JSON schema issue
  • SDK issue
  • Billing, credits, or rate limit issue
  • Dashboard, API key, or auth issue
  • Other API bug

Affected API area

  • Agent API
  • Search API
  • Sonar API
  • Embeddings API
  • SDKs
  • Dashboard, API keys, or auth
  • Billing or credits
  • Not sure

Summary

Expected behavior

Actual behavior

Minimal reproduction


Response or error


Request details

  • Endpoint:
  • Model or preset:
  • SDK/language/version:
  • Request ID:
  • Approximate time and timezone:
  • Consistent or intermittent:

Additional context

Hey @Anton_Verigin! The team is aware of the sandbox issue and is working on a fix. The ticket is still not closed, the support team will update you by email, when it’s done.