Skip to main content
Recruiters may update registration timings, but candidates may still see old changes. This indicates a delay or misconfiguration in syncing the updated duration.

​
🔎 Troubleshooting Common Issues

IssueHow to Fix It
Platform sync delayUpdated timings may take 1–2 minutes to propagate.
Refresh candidate view after waiting.
Browser caching old metadataAsk candidate to refresh using Ctrl + F5 or try **Incognito **mode.
Incorrect date/time updateVerify that the edited date/time was actually saved (in Recruiter view). Reapply changes if needed.
Candidate accessing a previously cached linkShare the newly generated link.
Old links may embed outdated expiry metadata.
Backend processes stuckIf new timing does not reflect after 5 minutes, contact Support with workflow ID

​
Pro Tip:

Test in a private window to confirm whether the issue is recruiter-side caching or actual backend mismatch.