Skip to main content
A workspace file is not searchable when it lands. Ingestion builds the derived representations (index, metadata catalog, optional knowledge graph).

​
States you will see

  • Uploaded, not ingested — list_files shows the row; search and QA will miss it or report it as not ingested.
  • Ingested — tools can read it. workspaces.stats reports counts by ingestion status.
  • Stale — the source bytes or labels changed after the last ingest. Call ingestion.ingest(..., stale_only=True) or reconcile.
  • Replaced — files.replace or on_conflict=new_version writes a new version and retires prior derived outputs.
  • Deleted — the file’s record is soft-deleted: it is kept with its metadata de-identified and no longer lists or resolves. The source bytes and all derived content are removed.

​
Retention

Workspace retention_policy sets TTLs for:
  • derived material (anchored on ingested_at)
  • source bytes (anchored on created_at)
  • job inputs, outputs and processing files (removed 48 hours after the job completes on a paid account, 7 days on a free account; job_ttl_days can only shorten this. A failed or cancelled job counts from the failure or cancel)
The policy is editable with workspaces.update. The console’s per-person Perception Playground workspace keeps files and job payloads for 7 days: files uploaded through the perception tools are deleted from platform-managed storage 7 days after upload. A playground’s source and job TTLs are capped at 7 days: workspaces.update stores a longer or unset TTL as 7 days, and a playground created under a longer policy is brought down the next time you sign in. Create your own workspace to choose a different policy. When a job result expires, GET /v1/jobs/{id} still exists but result is gone and reads raise result_expired. Granular POST /v1/uploads handles are separate: 24-hour default TTL, 7-day cap, deleted when the consuming job finishes. See Sources and uploads. For everything NDI keeps, where, and for how long, including zero retention and processing by model providers, see Data retention.

​
Inactive organizations

An organization created in the NDI console that is still on the free credit allowance may be deleted after 90 days without activity. Activity is any API request or console session in that organization, any job, and any new member or API key. Its owners are emailed first; the deletion starts no earlier than 14 days after that email, and only if the organization stayed inactive. Deletion removes all of its workspaces, files, results and API keys; only the anonymized metadata described in What we keep after deletion is kept. Organizations with a raised or unlimited credit allowance, and organizations set up by NDI or by a partner, are not affected.