Interpret DRAFT, COMPILING, READY, STALE, MAPPING_REQUIRED, INVALID, and FULL states.

Overview

Interpret DRAFT, COMPILING, READY, STALE, MAPPING_REQUIRED, INVALID, and FULL states. Template-management changes can affect every application that renders by template name or UUID. Make changes in a controlled environment and keep a source copy of production templates.

Key points

• READY indicates a compiled package is available.
• STALE means a relevant input changed.
• MAPPING_REQUIRED identifies unresolved placeholders.
• INVALID identifies structural or XSLT validation failure.
• FULL indicates no component compilation is needed.
• COMPILING should be temporary and monitored if it persists.

Recommended procedure

1. Open or retrieve the intended tenant-owned template.
2. Review its mode, output, resources, and compilation status.
3. Make the smallest necessary change and save it.
4. Validate, compile when required, and perform a sample render before use.

Troubleshooting

A saved template no longer renders

Check whether the edit made a composite template STALE and compile it again.

An imported template has a different name

The importer creates a unique tenant name when a collision exists.

A resource does not appear

Confirm the resource name, encoding, template UUID, and whether the downstream renderer supports that resource type.

Related documentation

• Full and Composite Templates
• Delete a Template
• Manage Template Resources

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.