After a PyjamaHR update, you may notice unexpected changes—such as missing candidate CVs, accounts being flagged for multiple logins, or a sudden drop in job responses. This article explains how to quickly identify, document, and report regressions so our team can resolve them efficiently. Following these steps ensures your hiring workflows remain smooth and your feedback drives platform improvement.

A regression is when a feature that previously worked as expected stops working after a product update. In PyjamaHR, recent customer reports have included:

These issues can disrupt your recruitment process, so it’s critical to report them with clear, actionable details. PyjamaHR’s support team relies on your reports to identify, prioritize, and resolve regressions quickly.

When to Report a Regression:
- You notice a feature behaving differently or incorrectly after a recent update.
- Mandatory fields (like CV uploads) are missing from candidate applications.
- Your account is flagged or restricted without clear reason.
- Job postings receive fewer applications or lower quality responses than usual.
- Any workflow that previously worked now fails or produces errors.

Integration with Other Features:
- Candidate Management: Missing CVs affect screening and shortlisting.
- Job Posting: Response drops may impact hiring timelines.
- Account Security: Unexpected flags can lock out recruiters or hiring managers.

Business Impact:
- Delays in hiring due to incomplete applications or missing data.
- Reduced candidate quality or quantity.
- Disrupted recruiter workflows and potential compliance issues.

Prerequisites:
- Access to your PyjamaHR account
- Details of the issue (JobID, CandidateID, screenshots, error messages)

Include the following details for fastest resolution:
- JobID(s): (e.g., https://app.pyjamahr.com/jobs/128021)
- CandidateID(s): (e.g., job_candidate=25363036)
- Description: What changed? What did you expect to happen?
- Screenshots: Attach images showing the missing field, error, or unexpected behavior.
- Frequency: Is this a one-off or recurring across multiple jobs/candidates?
- Recent changes: Did you notice this right after a PyjamaHR update?

Screenshot Callouts:
- Application detail page showing missing CV (highlight the empty field)
- Account flagged notification (highlight the error message)
- Job dashboard showing drop in applications

Do’s:
- Do provide as much detail as possible (JobIDs, CandidateIDs, screenshots).
- Do mention if the issue started after a specific update.
- Do follow up with additional examples if you find more.

Don’ts:
- Don’t report vague issues (“It’s not working”) without specifics.
- Don’t assume support is aware—always report new regressions.
- Don’t wait to report—early feedback helps fix issues faster.

Issue: Application missing mandatory CV
​ Solution:
- Check if the candidate applied via a third-party job board or direct link.
- Confirm if the CV field is set as mandatory in your job settings.
- Report affected JobIDs and CandidateIDs to support with screenshots.

Issue: Account flagged for multiple logins
​ Solution:
- Note if this happens across all jobs or specific ones.
- Provide your account email and affected JobIDs.
- Support will investigate and resolve any false positives.

Issue: Drop in job responses after update
​ Solution:
- Compare application numbers before and after the update.
- Report affected JobIDs and timeframes.
- Mention if you used Job Boost or other promotional features.

What if support asks for more details?
- Be ready to provide additional JobIDs, CandidateIDs, or screenshots.
- If unsure how to find these, ask support for guidance.

Recovery:
- Once the regression is fixed, review affected jobs/candidates to ensure data is restored.
- If critical data (like CVs) is missing, ask support about recovery options.

When to Contact Support:
- As soon as you notice a regression.
- If you’re unable to resolve the issue with the above steps.
- If the issue is blocking your hiring process.

1. What is a regression in PyjamaHR?
A regression is when a feature that previously worked stops working after an update.

2. How do I know if I’m experiencing a regression?
If something that used to work (like mandatory CV uploads) suddenly fails, it’s likely a regression.

3. What details should I include when reporting?
Always include JobID(s), CandidateID(s), a clear description, and screenshots.

4. Can I report multiple issues in one ticket?
Yes, especially if they’re related (e.g., missing CVs across several jobs).

5. How long does it take to resolve regressions?
Resolution times vary, but detailed reports help speed up the process.

6. What if I find more examples after reporting?
Reply to your existing support thread with new JobIDs or screenshots.

7. Will missing data (like CVs) be restored?
Support will investigate and attempt recovery, but restoration depends on the nature of the regression.

8. Why was my account flagged for multiple logins?
This may be a false positive after an update—report it with your account and job details.

9. I’m not getting enough responses for a job—could this be a regression?
If this started after an update, report the JobID and timeframe to support.

10. What if I have a quality issue with Job Boost?
Report the job, describe the quality issue, and mention if it started after an update.

11. Do I need to provide links or just JobIDs?
Providing both helps support investigate faster.

12. What if support doesn’t respond quickly?
Follow up in the same thread; urgent issues can be escalated.

Recommended Actions:
- Review your jobs and candidate applications after each major update.
- Bookmark this article for quick reference.
- See How to Submit a Support Ticket in PyjamaHR and Managing Candidate Applications for more details.

Still need help?
Contact PyjamaHR Support with your detailed report, and our team will prioritize your issue for resolution.

Keywords: regression, update issue, missing CV, account flagged, job response drop, PyjamaHR support, JobID, CandidateID, reporting bugs, application error