Job search
HackerRank Test Access Problems: Expired Links, Interruptions, and Retake Requests
Diagnose HackerRank assessment errors by separating expired invitations, canceled or inactive tests, capacity limits, and interrupted attempts before requesting recruiter action.
If a HackerRank test link fails, the message usually points to the next step: wait for the stated start time, ask the recruiter to extend an expired window, or report a canceled invitation. Record the exact error and when it appeared before retrying. If a test was interrupted after you started, explain what happened and ask the hiring team whether they want the existing attempt reviewed or a new invitation sent. HackerRank does not decide whether an employer grants a retake.
Start with the invitation email, not an old bookmark or a second account. Check the test name, the hiring company, the scheduled start and end times, and any timezone shown. A failed link can indicate a future start time, an expired window, a canceled invitation or a test status the hiring team needs to check.
For a practical way to keep your search moving while the issue is reviewed, browse recent roles on LandOffer.ai. Keep the test invitation and your application confirmation together so you can refer to the same role when you contact recruiting.

Match the message to the right action
HackerRank's candidate help page describes several different test-access errors. Use the exact wording on your screen to choose a response; a link that is not active yet needs a different action from one that expired after its deadline.
| Message or situation | What it can mean | First action |
|---|---|---|
| “Servers at capacity” | The platform has reached its concurrent candidate limit | Wait a few minutes and retry only if the invitation's login window is still open |
| “Invite cancelled” | The recruiter or hiring team canceled the invitation | Reply to the invitation and ask whether they intended to cancel it and can send a new one |
| “Test is not active at this time” | You tried before the scheduled start or after the test expired | Compare the invitation's start/end time and timezone; wait if the start has not arrived, ask the recruiter about an extension if it has passed |
| “Test is currently not available” | A recruiter may have edited the test and moved it from Published to Draft | Contact the recruiter and ask them to check the assessment status |
| Login or WebSocket error | Credentials, browser settings or network access may be blocking the session | Check the candidate troubleshooting steps, then send the exact error and what you tried |
| Page froze or connection dropped after start | The attempt may have started even if you could not finish normally | Stop repeated retries, record the interruption and contact the hiring team promptly |
These labels are based on HackerRank's current candidate troubleshooting guide. The hiring team owns the test window and decides whether to extend access, issue another invite or continue reviewing an attempt. Platform support can help diagnose a technical problem, but it cannot approve an employer's retake or change the employer's hiring workflow. HackerRank's candidate experience guidance says the recruiter or hiring team decides whether to offer a retest or continue the process.
Check the invitation's start time and timezone
Before changing your browser or trying an older URL, open the newest invitation and read its test name, start date, expiration date and timezone. A test that is scheduled for tomorrow in the employer's timezone can look unavailable if you check it tonight in yours. Compare the invitation's full date and time rather than relying on “today,” “tonight,” or a calendar event that has converted the time for you.
Write down both the timezone shown in the invitation and your local timezone. If the email lists a date without a zone, ask the recruiter to confirm the access window. Avoid guessing from the employer's office location or your laptop clock. HackerRank's employer-side settings allow test start and end times with a timezone, and invited candidates cannot access a test after it expires. The platform's expiration settings guide describes those controls; candidates cannot change them.
If the test has not started, wait until the stated time and open the link from the latest invitation. If the window has expired, ask the recruiter whether they can extend it and confirm the new end time and timezone in writing. Do not assume that an old link remains usable because the invitation is still visible in your inbox.
Handle a capacity error without losing the window
When the error says “Servers at capacity,” HackerRank recommends waiting a few minutes and trying again within the designated login window. Avoid refreshing repeatedly every few seconds; that adds noise without changing your place or the invite deadline. Keep the invitation open and note the exact time of the message.
If the message persists, check the window before spending more time on local troubleshooting. If there is still time, try one current supported browser and a stable connection. If the issue remains or the window is about to close, reply to the invitation with the exact wording, the time and timezone, and the browser/device you used. HackerRank's guide specifically says to contact the recruiter or hiring manager if the window expires while the capacity issue continues.
Do not switch to a public test URL, sign in with a company-side HackerRank account, or use another person's invite. Those are not substitutes for your private assessment invitation and could create a separate access or identity problem. Use only the candidate link the employer sent you.
When an invitation is canceled or the test is unavailable
A canceled invitation is different from a password problem. HackerRank says this message appears when the recruiter or hiring team cancels the test invite. Reply to that email or contact the recruiter, describe the message and ask whether they will send a replacement invitation. Do not repeatedly request a password reset if the page itself says the invite was canceled.
“Test is currently not available” can have a different cause. HackerRank says a recruiter edit after sending invitations can move a test from Published to Draft. Ask the recruiter to verify the assessment status and, if appropriate, republish it or send a new valid invitation. You do not need to diagnose the employer's configuration. Give them the test title, role and exact error so they can find the right assessment.
Use the original invitation thread when possible. It gives the recruiter context about which role and assessment you mean. If that email is missing, use the verified recruiting contact from the employer's official application or candidate portal; do not send personal information to an address found in an unverified forum or forwarded message.
If the test was interrupted after you started
A dropped connection, frozen editor or power outage does not tell you whether HackerRank saved your answers or whether the employer will accept another attempt. Note what you saw: whether the editor still showed your work, whether you clicked Submit, whether you received a completion screen or confirmation email, and whether the invitation now says the test was completed or already taken. Do not start a new attempt through a different link unless the recruiter confirms that is the intended next step.
Record the interruption time with its timezone and a short sequence: when you launched, when the problem began, what error appeared, what you tried, and whether you could reconnect. Include the browser, device, operating system and network type if relevant. If you saw a platform-wide status notice, capture its timestamp too. Keep the notes factual; do not label a local Wi-Fi issue as a HackerRank outage unless you have evidence of one.
The test timer may continue while you troubleshoot. HackerRank's employer-side documentation says the timer does not pause automatically for technical issues; the test owner or editor may be able to add time during or after an attempt, depending on the test. That is an employer control, not a promise that time will be restored. Ask the recruiter whether they would prefer the existing attempt reviewed, extra time if the session remains available, or a new invitation.
Before accepting a retake, ask how it will affect the existing attempt. HackerRank's reinvitation instructions say that a previous report is automatically deleted when the employer reinvites a candidate; recovery requires contacting HackerRank Support. If you finished or submitted part of the test, ask the recruiter whether the new invite is intended to replace that report and how recovery would be handled if the original attempt should be reviewed. A new invitation link does not give you a way to restore a deleted report.
Send a concise support request
Give recruiting enough detail to locate the right invitation without sending code, passwords or a full tokenized URL unnecessarily. A useful message includes:
- The role title and company, plus the HackerRank test name if shown.
- The invitation email's send date and the stated start/end time with timezone.
- The exact error text and the date/time it appeared, with your timezone.
- Whether you had started, submitted or received a completion confirmation.
- Browser, device and network details, and the one or two troubleshooting steps you tried.
- The action you are asking the employer to consider: confirm the window, issue a replacement invite, extend access or review the interrupted attempt.
For example:
I’m scheduled to take the HackerRank assessment for Backend Engineer. The invitation says it is open until 5:00 p.m. Eastern on October 14. At 4:42 p.m. Eastern, the page showed “Servers at capacity.” I waited five minutes and retried once in Chrome on my laptop, but the same message remained. I had not started the test. Could you confirm whether the window is still open or send an updated invitation if it has expired?
For an interrupted attempt, replace “I had not started” with what actually happened, such as “I submitted question two, then the editor stopped responding at 2:18 p.m. Pacific; I did not see a completion screen.” Ask whether the current attempt should be reviewed before anyone sends a retake. Keep the subject line specific and retain the message and reply with the assessment invitation.
Contact HackerRank Support when the issue is technical
The candidate help page includes steps for credential, browser, network and WebSocket errors. For example, it recommends checking supported browsers and, for a WebSocket issue, trying another network or disabling a VPN/proxy or browser extension if those changes are permitted on your device. Follow your employer's assessment rules and do not disable required security software or use a prohibited device.
You may also contact HackerRank Support for technical troubleshooting. HackerRank says it can record technical findings and review basic technical tickets, but it does not verify that you are part of a particular hiring process and does not notify the recruiter about an individual support ticket. Send the same issue summary to the hiring team so they know the access problem affected your scheduled assessment. If deeper investigation is needed, HackerRank's guidance says the recruiter or hiring team must escalate it.

If no one replies before the window closes
Send one brief follow-up in the existing invitation thread before the access deadline if you can. State when the window closes, include the error timestamp and ask whether the recruiter wants you to wait for a replacement link. If the window has already expired, document that fact and ask whether the employer can extend it. Do not submit the same assessment repeatedly or create a new candidate account to get around an invitation state.
Keep a copy of the original invite, your incident note, support ticket number if you contacted HackerRank, and the recruiter's instruction. When a new link arrives, verify that the sender and role match, note its updated start and end time with timezone, and use that link only once the recruiter has clarified how it relates to the earlier attempt.
The useful request is not simply “please reset it.” Tell the hiring team whether you could not start, were blocked by a capacity message, saw a cancellation, or lost access after beginning. Then ask for the specific decision you need: a corrected time window, a replacement invitation, an extension, or review of the existing attempt. The employer controls that decision; a clear incident record helps them see what happened and choose the next step.
For your next role from recent jobs on LandOffer.ai, save the application confirmation and assessment invitation together so a technical issue is easier to report accurately.
Sources and Further Reading
- HackerRank Candidates: Troubleshooting Test Login Errors — candidate-facing explanations for capacity, canceled invites, inactive tests and technical access errors.
- HackerRank: Ensuring a Great Candidate Experience — recruiter decision rights, escalation workflow and information to include in a platform-support request.
- HackerRank: Modify Test Expiration Time — employer-side test windows, timezone and expiry behavior.
- HackerRank: Reinvite Candidates to a Test — employer-side retakes and effect on the prior report.
- HackerRank: Extend Test Duration for Candidates — employer controls for adding time after technical issues and related restrictions.


