Troubleshooting

A route returns 404

Confirm its folder and static index.tpl. Nimbly loads a static route directly from its index.tpl by convention. For a dynamic route, inspect matched segments, validation and router_accept() or router_deny(), and run ./nimbly routes:sync when route definitions change.

An API request is denied

Check the integration user's API access, token expiry and role permissions. The response's needs field helps identify the required permission. On PHP-FPM verify forwarding of the Authorization header using the generated web-server configuration. Do not disable authorization to diagnose access.

Content renders incorrectly

Inspect the resource field type and its metadata, language values and output shortcode. Use [#get-html#] for configured rich content. Keep conditional markup in a separate template: [#if#] has no block form.

A value does not change

[#set#] keeps an existing value by default. Add overwrite only when replacing it is intended. For stale records inspect resource caching and indexes before adding a second persistence mechanism.

Assets look stale

Confirm the build inputs, run ./nimbly build, and verify the environment serves the generated assets. A framework checkout update can require a new asset build.

Jobs or email do not run

Inspect the jobs administration view, scheduler installation and environment mail configuration. Check the actual job error and delivery result. Use the integrated scheduler described in jobs operation and the delivery configuration in email.