Errors
404 - schema not registered
What happened
The named schema is absent from the selected tenant or namespace.
- Check the current connectionConfirm the instance and tenant.
- Find the qualified schemaCompare the namespace and table with the schema list.
- Correct the name or registerCreate the intended missing schema with its dependencies.
- Verify the requestConfirm it now uses the expected schema.
Request that triggers it
A direct GET against a schema id that doesn't exist.
curl "https://$OC_HOST/v1/tenants/$OC_TENANT/schemas/does.not.exist" \
-H "Authorization: Bearer $OC_TOKEN"Read the response
{
"error": "schema_not_found",
"message": "no schema 'does.not.exist' for tenant",
"retry": false
}Fix the request
- Check the qualified schema name.
- List schemas on the current connection.
- Register missing referenced schemas first.
- Register or select the intended schema and retry.
Keep in mind: Schema definitions in another tenant do not satisfy this request.
Common causes
- Schema registered on staging but not yet on prod.
- Typo in the namespace -
shop.vsshops.. - Schema was deleted (via a destructive-data confirm) and a downstream service still references it.
- Multi-region deploy where the new region missed a migration step.
Continue
See error handling and retries, or return to error examples.