Articles

What Happens If Your Internet Disconnects During an OA? Recovery, Evidence, and Recruiter Email

Internet disconnected during an OA? Learn how to preserve evidence, reconnect safely, request a reopen or extra time, and email the recruiter.

If your internet disconnects during an online assessment, do not assume that your attempt is automatically lost or automatically saved. The result depends on the platform, the point at which the connection failed, whether your code or answer was submitted, and the hiring company’s recovery policy. Your safest first move is to keep the assessment tab open, record the time and visible error, and reconnect without opening outside help.

Some platforms let a recruiter add time or reopen the session. HackerRank documents both options, while Codility tells candidates to contact the test administrator so the session can be reopened from the last submitted code. CodeSignal tells candidates to contact CodeSignal support and the company contact when an interruption affects an assessment. These are recovery paths, not promises that every platform will restore a timed attempt.

Quick answer: what to do when the connection drops

Moment	Action	Why it matters
The page stops responding	Stop clicking repeatedly; keep the tab and browser open	Repeated refreshes or closing the tab can make recovery harder and may discard local state
You see an offline or reconnecting message	Note the exact time, question, timer value, and message; take a screenshot if possible	The platform and recruiter need a precise timeline, not “the test broke”
The connection returns	Use the same tab or original invitation link, then check whether your latest code or answer is present	A new attempt can create a different session or overwrite evidence
The timer continued	Finish only if the session is stable and the rules allow it; otherwise contact the administrator immediately	Some platforms keep the timer running during technical problems
The deadline expires or the session is locked	Do not create a duplicate attempt unless the employer authorizes it	A second invite, reopen, or retake can change how the report is recorded
You need an accommodation	Tell the recruiter or platform support before the deadline when possible	The company, not a generic blog post, decides whether time or a new attempt is granted

There is no universal OA recovery rule

“Online assessment” describes a hiring step, not one product. A coding test, questionnaire, video response, and proctored exam can all behave differently when connectivity fails. Employers can also choose different timers, proctoring, desktop-app, and reopen settings. Do not rely on a claim that an OA “always autosaves” or “always gives a retake”; ask about the specific invitation.

Separate three states:

Draft work: text in an editor or answer box that may not have reached the server.
Submitted work: a solution or answer the platform confirms and associates with the attempt.
Final result: the report or score the employer receives after processing.

A connection loss can affect the transition between these states. A green “submitted” confirmation is stronger evidence than code visible on screen. A final result is stronger evidence than either, but it may appear only after the platform finishes processing.

What major platforms document

HackerRank

HackerRank’s employer documentation says the test timer runs continuously and does not pause for technical issues. A test owner can add extra time during the test, after submission, or after the test ends. HackerRank also documents reinviting a candidate after a power or internet loss, but the previous report is automatically deleted when the candidate is reinvited. Ask about that trade-off before accepting a new invitation.

If the test uses Secure Mode or another integrity mode, the employer may also receive behavior and session signals. A connection drop can therefore be both a time problem and an integrity-review question. Explain the interruption factually; do not try to work around the test in another browser or device unless the recruiter authorizes it.

Codility

Codility tells candidates to contact the test administrator and ask for the session to be reopened. Its employer guidance says a reopened session uses the same invitation link and restores previously submitted code. Reopening overrides the previous score for reopened tasks, and the employer decides whether to do it. A browser reload or unfinished editor buffer is not the same as an approved reopen.

CodeSignal

CodeSignal provides a connection test before a proctored session. For an interruption, it tells candidates to contact support@codesignal.com promptly and alert the company contact. Its public documentation does not promise one universal offline-save or timer-pause behavior, and a proctored outage may affect screen sharing, camera, microphone, and identity checks as well as the editor.

What to do in the first five minutes

1. Freeze the state

Do not close the browser, clear cache, switch to a private window, or start a second attempt. If the page is still visible, leave it open. Note the local time, question number, timer value, and the last action you took, such as clicking Submit or Run.

2. Capture evidence

Take a screenshot of the error or offline banner, the timer, and the assessment URL if they are visible. If the whole screen cannot be captured because of proctoring rules, write down the details instead. Keep your network-status screenshot, router log, or mobile-hotspot timestamp only if it does not violate the assessment rules.

3. Reconnect using the approved path

Reconnect to the same network if possible. If the invitation or help page specifically permits a hotspot, use it; otherwise ask the administrator. Return through the same tab or original link. Do not open search results, forums, an AI tool, or an external IDE while the assessment is active.

4. Verify before continuing

Check whether the timer is still running, whether the last submitted answer is present, and whether the platform shows a saved or submitted confirmation. If the code is missing, stop and contact support instead of guessing which version the system received.

5. Escalate quickly

If the connection does not return within a few minutes, or if the timer is consuming time while the page is unusable, send the recruiter or test administrator a short factual report. Use the platform’s support channel too when the documentation provides one.

What evidence should you send?

A useful incident packet is short and specific:

exact assessment name and job or requisition ID;
invitation email address, if needed to locate the attempt;
date and local time of the interruption, including time zone;
question or section open at the time;
timer value before and after reconnecting;
whether you had clicked Submit or received a save confirmation;
the visible error text or a screenshot, if allowed; and
the steps you took to reconnect.

Do not attach source code, assessment questions, identity documents, passwords, or one-time login codes unless the platform’s secure support process explicitly requests them. A network outage report should explain the interruption, not disclose the test content.

Recruiter email template

Send one clear email to the person or address in the invitation. You can adapt this template:

Subject: Technical interruption during [assessment name] – [job ID]

Hello [name],

I was completing the [assessment name] for [job title, job ID] on [date] at approximately [time and time zone]. My internet connection dropped while I was on [question or section]. The timer showed approximately [time remaining]. I [received a save/submit confirmation or did not receive one], and after reconnecting I saw [exact status or error].

I have attached [a screenshot or no attachment] and have not started a second attempt. Could you please confirm whether the existing session can be reviewed, reopened, or given additional time? I am happy to follow the platform’s support process.

Thank you, [name]

The phrase “I have not started a second attempt” is useful because it tells the recruiter that the original evidence remains identifiable. If you already restarted, say so plainly and include both timestamps.

Timers, saved code, and reopens

Candidates often ask whether a connection loss pauses the clock. The answer must be platform-specific:

Question	Safe answer
Does an internet outage pause the timer?	Do not assume it. HackerRank explicitly says its timer runs continuously during technical issues; other platforms may behave differently.
Is code in the editor saved?	Only treat it as protected when the platform shows a save or submission confirmation, or the platform’s documentation promises local recovery.
Can I refresh?	Follow the platform’s support instructions. A refresh may reconnect, but it can also remove an unsent editor state.
Can the recruiter add time?	Some platforms support it. HackerRank documents extra time; the employer must authorize and apply it.
Can the session be reopened?	Codility documents administrator-controlled reopening from previously submitted code. Other platforms may require a new invite or support review.
Should I retake immediately?	No. Wait for the employer’s instruction so the original report is not overwritten or treated as a duplicate.

Accessibility and accommodation requests

If a disability, shared connection, or approved accommodation affects your setup, ask before starting whenever possible. Tell the recruiter what support you need—extra time, a technical check, or a new session—without disclosing medical details to a general support inbox. An accommodation request and an outage reset may be separate processes.

Frequently asked questions

Will an internet outage automatically fail my OA?

Not necessarily. Some employers can add time, reopen a session, or reissue an invitation. Others may treat an incomplete or unsubmitted attempt as final. The platform and employer decide; contact them promptly with evidence.

Should I refresh the assessment page?

Only when the platform’s instructions tell you to. Keep the original tab open first, record the state, and avoid a refresh that could discard unsent work. If you must refresh, use the same session and confirm what was saved before continuing.

Does a recruiter see that my internet disconnected?

The report may contain timestamps, session events, or an incomplete attempt, depending on the platform and settings. Do not assume the system will explain the outage automatically. Send the recruiter a factual timeline so they can interpret the record.

Can I use a phone hotspot after Wi-Fi fails?

Use one only if the assessment rules and support instructions allow it. A network change does not authorize opening another device, searching for answers, or bypassing proctoring controls.

What if my code was visible but not submitted?

Tell the administrator exactly that. Visible editor text is not the same as a server-confirmed submission; ask whether a controlled reopen is available.

The practical takeaway

When an OA loses internet, preserve the session, capture the evidence, reconnect through the approved path, and contact the test administrator before starting anything new. HackerRank, Codility, CodeSignal, and other vendors expose different recovery controls, so platform-specific instructions matter more than a generic promise of autosave. A concise timeline and a professional email give the employer the information needed to add time, reopen the session, or decide on a fair next step.

Sources and Further Reading

Research note: checked September 6, 2026. Timers, save behavior, proctoring, reopen controls, and retake decisions vary by platform, employer configuration, and assessment type. The invitation and test administrator control the candidate’s actual recovery path.