Articles
HackerRank Test Cases Not Loading: Browser Fixes, Evidence, and Deadline Recovery
Troubleshoot HackerRank loading failures: distinguish hidden cases from errors, refresh once, preserve the attempt, and request a review of lost time.
For a blank HackerRank question or results panel, refresh the browser once. HackerRank's during-test FAQ recommends refreshing when questions or images fail to load and says progress and submitted answers are preserved. Do not log out as a troubleshooting step: the same FAQ says logging out ends the attempt.
A locked hidden test is different from a loading failure. If the timer is running and refreshing does not help, report the problem promptly.
Is it a hidden case, a code error, or a broken panel?
| Symptom | Likely category | Next step |
|---|---|---|
| A hidden case has a lock icon; other controls work | Deliberately concealed test data | Debug from constraints and permitted custom input |
| A compile error or time-limit error appears | Execution or solution issue | Read the message; inspect syntax, complexity, or input handling |
| The question, images, or result panel remain blank | Loading problem | Refresh once, then report if unresolved |
| Run stays pending without a result | Execution request may be delayed or stuck | Note the time and error; report persistent failure rather than repeatedly submitting |
HackerRank's test-case documentation distinguishes sample, hidden, and custom tests. Hidden input is not supposed to become visible after a browser fix. Passing the sample also does not establish correctness on every hidden test.
For example, a solution may handle three positive numbers but fail an empty input or repeated value allowed by the prompt. That is a test-design problem to investigate. A result panel that never returns any status is an environment symptom. Describe which one occurred when contacting support.
When the test timer is already running
- Note the error and approximate remaining time. If the rules permit a screenshot, capture only the error, without exposing the prompt or source code. Do not delay the first refresh to build a detailed incident report.
- Refresh once. HackerRank documents this recovery step; you do not need to wait for a recruiter to approve it. Do not interpret progress preservation as permission to leave unsaved work indefinitely.
- If it remains broken, use ? → Report a problem in the test and notify the recruiter with the lost-time estimate. The timer continues through a disconnection; a support ticket does not pause it.
The FAQ also suggests a private window and clearing cache/cookies for loading issues. These are more disruptive during a monitored, timed attempt: use the test's specific support instructions before changing sessions or clearing active authentication. Before the test starts, they are reasonable isolation steps. Avoid switching programming languages to fix a spinner, because that can reset the editor.
What extra time can and cannot do
Authorized employer users can add time during or after an attempt under HackerRank's extra-time workflow. Ask for review of the incident and the appropriate remedy; do not promise yourself a timer reset. If extra time is granted, refresh to see the updated timer.
Invitation expiry, an ended attempt, and a purged development environment are not interchangeable. A replacement invitation may be necessary for some environments. Keep the recruiter response so you know whether to resume the existing attempt or use a new one.
A message that lets support act
Subject: HackerRank loading failure during [assessment] — [name]
At [time, timezone], [question/results panel or Run action] stopped responding. The timer showed about [X minutes]. The error was “[exact text]”; [other questions still worked / the whole test was unresponsive].
I refreshed once at [time], with [result]. I use [browser/version] on [OS]. My support reference is [if available]. Could you review the lost time and confirm whether I should continue this attempt or use another recovery step?
Send this to the official support route and the original recruiting contact as appropriate. No assessment questions, solution code, or credentials are needed in the initial message. After recovery, verify the timer, saved work, and submission state rather than assuming that pressing Run submitted the answer.
Sources and Further Reading
Documentation checked: September 6, 2026.