Skip to content

Troubleshooting Indexing Errors

If your search isn't returning expected results, the data might be there but not properly indexed. OSDU assigns an indexing status to every record — if indexing failed, the record won't appear in search results.

Indexing status codes

Status code Meaning
200 Record indexed successfully
404 Schema is missing in the Schema service
400 Field type mismatch — e.g. schema expects an integer but the record has a text value

Finding records with indexing errors

Search for records with a 404 indexing error (schema missing):

osdu search query -q "index.statusCode:404" --limit 1000 --filter "results[*].{id:id,status:index.statusCode}" -o json

Search for records with a 400 indexing error (field mismatch):

osdu search query -q "index.statusCode:400" --limit 1000 --filter "results[*].{id:id,status:index.statusCode}" -o json

Search for all records with any indexing error:

osdu search query -q "index.statusCode:400 OR index.statusCode:404" --limit 1000 --filter "results[*].{id:id,status:index.statusCode}" -o json

Records with a 404 error (schema missing):

{
  "kind": "*:*:*:*",
  "query": "index.statusCode:404",
  "limit": 1000,
  "returnedFields": ["id", "index"]
}

Records with a 400 error (field mismatch):

{
  "kind": "*:*:*:*",
  "query": "index.statusCode:400",
  "limit": 1000,
  "returnedFields": ["id", "index"]
}

All records with any indexing error:

{
  "kind": "*:*:*:*",
  "query": "index.statusCode:400 OR index.statusCode:404",
  "limit": 1000,
  "returnedFields": ["id", "index"]
}

What to do next

  • 404 — Schema missing: The record's schema kind is not registered in the Schema service. Check that the schema exists and is correctly published.
  • 400 — Field mismatch: The record has a field value that doesn't match the schema definition (e.g. a string where an integer is expected). Inspect the record and correct the data or update the schema.

If you're unsure how to resolve the issue, contact the OSDU Platform Team on Slack.

Last update: 2026-02-27