For candidates
My one-way interview did not submit. What now?
One answer failed to upload, the page froze, or the link expired mid-recording. Here is exactly what to do, who to email, the words to send, and whether one failed upload actually sinks you.
If a one-way interview did not submit, email the recruiter or the platform’s support address right away. Name the exact question or step that failed, and ask them to reset your link or confirm what was recorded. A technical glitch is not a verdict on your answers, and most teams will reopen the interview if you flag it quickly.
That is the whole answer. The rest of this page is the detail: how to tell what actually went wrong, the exact email to send, who to send it to, and the honest read on whether one failed upload costs you the job. (Short version on that last one: it rarely does.)
First, breathe. This happens constantly
You are not the first person this happened to, not by a long way. People describe the exact same moment all the time. One candidate posted that a single video out of eight questions did not submit and asked, flatly, “will they reject me?” Another asked for advice on an “incomplete hirevue interview.” A third said the interview “expired mid-interview” and they were left staring at a dead page.
The format is fragile in small ways. Uploads stall on weak Wi-Fi. Browser tabs time out. A recording link has an expiry window that nobody tells you about, and it lapses while you are mid-sentence. None of that is a verdict on you. It is a glitch in a tool, and tools glitch.
So before you do anything, separate two questions in your head. Did your answers go badly? That is a different page (we will point you to it). Did the technology fail? That is this page, and it is almost always fixable.
Work out what actually happened
A few seconds of diagnosis makes your email far more useful. Look for which of these you are dealing with.
- One answer is missing, the rest went through. You completed the interview, but one clip shows as not uploaded or stuck on “processing.” This is the most common case and the most fixable.
- The whole thing failed to submit. You recorded everything, hit submit, and got an error or a spinning wheel that never resolved. The recordings may still be saved in the browser or on the platform’s side.
- The link expired or timed out mid-interview. You were partway through and the session died. You cannot get back in.
- The page froze or crashed during a recording. You do not know whether that answer saved at all.
- It says submitted, but you are not sure. The confirmation was ambiguous, or you closed the tab too fast.
Whatever it is, do not start re-recording everything in a panic, and do not assume the worst. Note the specific question number or step where it broke. That detail is the single most useful thing you can give a recruiter.
Take two quick steps before you email
These take a minute and sometimes solve it outright.
- Do not close or refresh the failed tab yet if it is still open. Some tools hold the recording in the browser and will retry the upload on a stable connection. If you have a weak signal, move closer to the router or switch to a wired connection or your phone’s hotspot, then let it try again.
- Screenshot what you see. The error message, the “not submitted” status, the timestamp. This is your evidence that it was a technical failure and not a missed deadline. It makes your email instantly credible.
If a retry works, great, you are done. If it does not, move to the email. Do not keep hammering the same broken page for an hour. A clear message to a human is faster.
Who to email, in order
You have two possible contacts. Use both if you can.
- The recruiter or hiring contact first. They own the decision and they can almost always reset your invitation or extend the deadline. Their address is usually in the original invite email, the one with the interview link.
- The platform’s support address second. Tools like HireVue, Spark Hire, Willo, and VidCruiter have a support email or help link, often in the footer of the invite or on their site. Support can confirm what was actually captured on their servers, which sometimes reveals that your answers saved fine after all.
If you only have one of the two, use that one. The recruiter is the more important contact, because they are the person who decides what happens next.
The email to send
Keep it short, factual, and free of apology spirals. You did nothing wrong. Here is a template you can adapt.
Subject: Technical issue with my one-way interview, [Job title]
Hi [Name],
I completed the recorded interview for the [Job title] role today, but I ran into a technical problem. [Question 3 would not upload and is still showing as not submitted / the link expired while I was partway through / the page froze during one of my answers.] I have a screenshot if it is useful.
I would like to finish this properly. Could you reset my link or let me know whether you can see what was recorded? I am happy to re-record [the missing answer / the whole interview], whatever is easiest on your end.
Thanks for your help, [Your name]
Why this works:
- It names the exact failure. “Question 3 would not upload” is something a recruiter can act on. “It didn’t work” is not.
- It offers a fix instead of asking for forgiveness. You are making it easy to say yes.
- It does not grovel. One clean apology is plenty. Eight is a red flag of its own.
Send it the moment you notice the problem. A message that lands within the hour reads as a genuine glitch. One sent three days later, after the deadline, is a much harder thing for a recruiter to reopen, even if they want to.
Does one failed upload actually cost you the job?
Almost never, and here is the honest reasoning.
Recruiters and the platforms know these tools fail. Dropped uploads and expired links are ordinary support tickets, not rare events. A candidate who hits a glitch, flags it calmly, and offers to fix it does not look careless. If anything, handling a small technical mess cleanly is a mild point in your favor, because it is exactly the composure the job will ask of you.
The case where a missing answer matters is narrow: if the role is highly competitive, the field is strong, and your other answers were only okay, a recruiter has less reason to chase down a missing clip. Even then, a quick, specific email usually gets you a reset. The thing that genuinely hurts you is silence. If you say nothing and one answer is blank, the recruiter has no way to know whether it was a glitch or a no-show.
So the rule is simple. The failure rarely sinks you. Not reporting it is what does.
If you genuinely missed the deadline too
Sometimes the technical failure and a missed deadline collide. The link died, you got busy, and now the window has closed. Email anyway. Be honest, be brief, and do not invent a more dramatic excuse than the truth. People recover from this. One person who completely missed a scheduled interview wrote it up as a personal disaster, and the common reply was the same: send a short, honest note asking for another shot. Plenty of recruiters give one. The worst outcome of asking is a no, which is exactly where you already are if you stay quiet.
While you wait to hear back
You have done the part you control. Now sit with the uncertainty without feeding it.
- Do not email five times. One clear message, then give them a working day or two. A reminder after that is fine. A barrage is not.
- Do not re-record the whole interview unprompted unless the recruiter asks for it. You might overwrite a version that was actually fine.
- Do not read silence as a rejection. If your application still shows as “in screening” or “under review” a few days later, that is normal pacing, not a verdict. These reviews take time.
A failed upload feels like the end of the process. It is almost always just a five-minute detour. You flag it, they reset it, you finish it.
If the real worry underneath this is not the glitch but how your answers came out, read what to do when you think you bombed a one-way interview. And if you are not sure how many do-overs you had in the first place, here is how retakes actually work.