Job portal & application issues
Why a posting isn’t visible, why an application didn’t arrive, and form errors applicants see.
A job isn't showing on the portal
- The posting must be published — drafts and closed postings don't appear. Check the job's Advertising tab: a live posting reads Live on your job portal.
- The portal itself must be enabled — check Portal enabled in Settings → Job board (when off, the portal returns "not found").
- Confirm the URL slug — if you changed the portal slug, old links 404. Re-share the current link.
An application didn't arrive
- Open the applicant review page — Applicants on the Jobs page, or the New applicants lane on the job's pipeline board — and check Needs decision, Screened out, Stored, Declined and Added. An applicant may have been actioned by a teammate or screened out as junk. See Reviewing inbound applicants.
- Duplicate suppression: the same email applying to the same posting within 24 hours is deduplicated by design.
- Give processing a minute — parsing and scoring run in the background; the job owner is notified when the applicant is ready.
- For LinkedIn applicants, see Email sync issues — capture depends on the receiving inbox syncing.
Errors applicants see on the form
| Symptom | Cause |
|---|---|
| CV won't upload | Only PDF/DOC/DOCX up to 10 MB are accepted. |
| "Too many requests" | Rate limiting — several rapid submissions from one network (campus wifi, office NAT). Wait briefly and retry. |
| Asked to confirm storage of details | When the portal requires it, applicants must tick the box allowing their details to be stored for the role before submitting. The separate marketing checkbox is optional. |
| Form rejects submission | Invalid email format, or the posting closed between page load and submit. |
If an autofill tool completes the hidden spam-trap field, Kepler rejects the submission. Ask the applicant to retry without autofill.