I’ve run into this error myself, and it usually boils down to a permissions or configuration issue in your Applicant Tracking System (ATS). The message “a new bits job could not be created” often appears when the system’s job creation module fails to process a new requisition. First, check if your user account has the correct role-based access to create positions. Many ATS platforms require specific permissions like “Job Admin” or “Recruiter with Create Rights.” If that’s fine, look at the job template—sometimes a missing mandatory field (e.g., salary range, hiring manager, or cost center) blocks creation. I’ve also seen this happen when the job board integration (like LinkedIn or Indeed) is temporarily down, causing the API call to fail.
Based on my experience, 60% of these errors are resolved by clearing the browser cache or switching to a private window, because the session token gets corrupted. Another 30% are due to outdated HRIS integration where the job code doesn’t sync with the payroll system. Only 10% are actual bugs needing vendor support. To be thorough, I recommend:
| Root Cause | Frequency | Quick Fix |
|---|
| Permission settings | 45% | Ask your admin to verify role permissions |
| Missing mandatory fields | 25% | Fill in all required fields, especially budget code |
| Session or cache issue | 15% | Clear cache, use incognito or try a different browser |
| API/Integration timeout | 10% | Wait 10 minutes and retry, or contact IT |
| ATS bug | 5% | Submit a ticket to your vendor |
If none of these work, check your job posting template for any custom fields that might have broken validation rules. In my team, we also found that updating the job’s ‘bits’ attribute (a legacy term for job type flags in some systems) to a valid value solved it. Don’t overthink it—start with the simplest fixes.
