Diagnose common HTTP statuses and FeraRender error codes.

Overview

Diagnose common HTTP statuses and FeraRender error codes. 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

• 400 identifies validation or invalid template input.
• 401 identifies missing authentication or failed permission.
• 404 identifies an unknown tenant-owned object.
• 406 identifies an unsupported response type.
• 409 identifies a stale composite template.
• 500 and 502 identify internal or downstream renderer failures.
• Use the stable code and message together.

Recommended procedure

1. Locate the relevant object, status, permission, or code.
2. Confirm tenant and version context.
3. Apply the documented rule consistently.
4. 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

• FeraRender Known Limitations and Review Items
• Configuration, MIME Types, and Compatibility Reference
• Permissions, Actions, and Error Codes 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.