Reference compilation records, resources, states, and transitions.
Overview
Reference compilation records, resources, states, and transitions. Use this article as a field and behavior reference. Verify release-specific values against the current service before publishing exact versions or product limits.
Key points
- Compilation records include template UUID, compiler version, dataset version, checksum, status, validation, and resource UUID.
- Compiled output is stored as compiled-package.
- The manifest is stored as compiled-package-manifest.
- READY can become STALE after source changes.
- MAPPING_REQUIRED and INVALID must be corrected before rendering.
Fields
| Field | Type or value | Purpose |
|---|---|---|
| templateUuid | UUID | Compiled template. |
| compilerVersion | string | Compiler implementation identifier. |
| datasetVersion | integer | Dataset version at compile time. |
| checksum | string | Compiled-content SHA-256. |
| status | string | Compilation result. |
| validationJson | JSON text | Warnings and errors. |
| compiledResourceUuid | UUID | Stored compiled-package resource. |
Recommended procedure
- Locate the relevant object, status, permission, or code.
- Confirm tenant and version context.
- Apply the documented rule consistently.
- Escalate conflicts between this reference and current API behavior for documentation review.
Troubleshooting
The documented value differs from a response
Record the service version and route, then update the draft or implementation before publication.
A field appears unused
Check legacy routes, UI clients, imports, and migration code before removing it.
A status persists unexpectedly
Inspect validationJson, compiled resources, assignments, and recent source changes.
Related documentation
- Permissions, Actions, and Error Codes Reference
- Configuration, MIME Types, and Compatibility Reference
- FeraRender Error Code Reference
Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.