Skip to main content
This page covers job detail pages built in the CMS — a page template bound to a job via a Job resource. If instead your jobs are missing from a job search or listing, that’s usually an ATS sync issue: see Why aren’t my jobs showing on the careers site?. Work through the symptom that matches what you’re seeing.

​
Preview says “Set dynamic parameters to preview”

Your slug has a dynamic segment (e.g. /job/:id), and the preview needs to know which job to load. Fix: Enter a real, live job ID in the id field in the preview toolbar. Copy the ID from Hiring → Jobs.

​
Preview works, but the live page 404s

The live site only ever serves the published version of a page. Fix: Click Save & publish. If you’re deliberately checking a draft, you can preview it on the live URL by appending ?ref= with the version reference, but the public URL won’t work until you publish.

​
The page loads, but says “This job is not available”

The Job resource fetched an ID that doesn’t resolve to a job for this company. Fix — check each of these:
  • The Job ID in Settings → Resources is {{params.id}} for a dynamic page, not a hard-coded number.
  • The ID in the URL is a real inploi job ID from Hiring → Jobs (the public lookup accepts the inploi job ID or the ATS external_id, not the external_ref).
  • The job belongs to this company — an ID from another company’s account won’t resolve.
  • A Job resource Condition isn’t deliberately returning a 404 (for example a rule hiding custom_data.is_internal jobs).

​
The page loads, but job details are blank

The content references {{resources.job.*}} values, but there’s no matching data. Fix:
  • Make sure a Job resource exists in Settings → Resources and its Resource key is job (the default). If the key differs, your tokens must match it — e.g. a key of role means {{resources.role.title}}.
  • Check the field names. Type {{ in the field to see the exact values available for this page.
  • Confirm the job actually has that field populated in your ATS (custom fields especially).

​
The page redirects somewhere unexpected

A Redirect resource is configured on the page, sending visitors elsewhere before the content loads. Fix: In Settings → Resources, remove the Redirect resource or correct its target URL.

​
I can’t see the Resources or Sitemap sections at all

These are restricted settings, only visible to users with full page update access. Fix: Ask an administrator to review your permissions (see Users and permissions).

​
The whole page errors

A page-wide error (rather than a “job not available” message) usually means the careers site can’t reach the jobs API — most often a missing or misconfigured publishable API key for the company. Fix: Contact inploi support so they can check the company’s API key configuration.