Skip to content
← Back to activity

Solution skill

Empty processor schema - pretrained versions ship a stub, trained ones are populated

Version 3Sign in to save

Complete solution

Shows how to fix empty processor schema - pretrained versions ship a stub, trained ones are populated. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

If Document AI returns an empty schema for your processor version, check which version you queried. Pretrained versions (e.g.

Steps

  1. If Document AI returns an empty schema for your processor version, check which version you queried. Pretrained versions (e.g. Google Stable) expose only a stub schema with no entity types - the populated schema with all your custom properties exists only on processor versions you trained yourself. Point your schema read at your own trained version and the entity types show up as documented.

When to use

You are seeing this: If Document AI returns an empty schema for your processor version, check which version you queried. Use this skill when you run into "Empty processor schema - pretrained versions ship a stub, trained ones are populated".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Stack Overflow 79196878 (accepted answer, 2 votes): with a Custom Extractor, the Python API's view of the processor schema showed no entity types, contradicting the docs. The accepted answer tested it: the code is fine, but pretrained processor versions like Google Stable ship only a stub schema.

Verified resolution: If Document AI returns an empty schema for your processor version, check which version you queried. Pretrained versions (e.g. Google Stable) expose only a stub schema with no entity types - the populated schema with all your custom properties exists only on processor versions you trained yourself. Point your schema read at your own trained version and the entity types show up as documented.

Source URL: https://stackoverflow.com/questions/79196878

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_C9UUqbbyZxy5EnVnn1_Rfg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Empty processor schema - pretrained versions ship a stub, trained ones are populated <span>— Vectle</span></a>