Respond when a previously compiled template becomes stale.

Overview

Respond when a previously compiled template becomes stale. Composite templates improve reuse but add a publish-time compilation step. Treat component and assignment changes as release events.

Key points

• Template content changes can invalidate compilation.
• Assignment changes invalidate compilation.
• Updating an assigned component invalidates dependent templates.
• A stale composite template returns TEMPLATE_COMPILATION_REQUIRED during render.
• Validate and compile again rather than attempting an automatic production workaround.

Recommended procedure

1. Confirm the base package and body are compatible.
2. Select active preamble and postamble components.
3. Set deterministic placement order.
4. Scan, validate, compile, and render a regression sample.

Troubleshooting

Compilation reports a declaration conflict

Rename or centralize variables, parameters, or named templates that share a name but differ in content.

The component order is rejected

Use unique sort-order values within PREAMBLE and POSTAMBLE.

Rendering returns TEMPLATE_COMPILATION_REQUIRED

The compiled package is absent or stale; validate and compile before rendering.

Related documentation

• Validate and Compile a Composite Template
• Order Preambles and Postambles
• Assign Components to a Template

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.