A submission that shows as "Failed" did not reach your upload destination. Usually the files are still held and a retry delivers them, so a failed submission is typically a few minutes of work rather than a lost upload. The exception is a submission where the uploader never finished sending anything. That one needs to be submitted again. This page covers how to find a failure, read its cause, fix it, and retry. Everything on this page is available on all plans.
Every upload form keeps its own record on the Submissions tab, and the "Status" column there shows how far each submission got on its way to your upload destination.
The "Status" column describes how far a submission got on its way to your upload destination. Expand a row for details.
Click the chevron at the left of a failed submission to expand it.
When the destination refused the files, a red banner sits at the top of the expanded row. It is headed "File couldn't be delivered," or names the number of files if more than one failed. Beneath the heading it reads "The destination rejected the upload. Try again, or fix the issue and retry." Click Technical details in the banner to see the exact reason recorded for the transfer. That reason tells you which fix below applies, so read it before retrying.
When the uploader never finished sending any files, the expanded row reads "This upload was never completed." and has no Technical details toggle. There is nothing to retry, so ask them to submit again.
These are the reasons the failure banner gives, and what each one means.
Most failures that will not clear on their own come back to the connection. A cloud account can stop working because its access was revoked at the provider, because a password change ended it, or because the account was removed.
Reconnecting automatically retries the submissions that failed on that account. You do not have to go back and retry them one at a time.
FTP and SFTP connections work differently, because they hold the server details you entered rather than a sign-in with a provider. The menu item on those reads Edit, and you correct the address, user name, or password in the dialog it opens.
EZ File Drop also emails you about a connection that has been failing, so a form that has quietly stopped delivering does not go unnoticed.
A folder that has been moved, renamed, or deleted in your cloud storage cannot receive files, and the transfer fails without being retried. Set the destination again on the form, then retry the failed submissions.
A form with more than one File Upload field has a destination for each one, so check them all.
There are two controls, and they do the same thing.
The submission moves back to "Transferring" and a "Transfer restarted" message appears. If the cause is still there, it fails again with a new reason, so fix the cause first whenever the reason gives you something to act on.
Retrying needs edit access to the form. A teammate with view access can see the control but gets an error when they use it. See Set form permissions.
A retry does not count against your team's monthly upload allowance a second time. See How bandwidth works.
A transfer that fails for a reason that might clear by itself is retried automatically, five more times, before it is left for you. The gaps between attempts grow: 1 minute, then 5 minutes, then 15 minutes, then 1 hour, then 6 hours. A destination that was briefly unreachable usually clears in the first attempt or two without you doing anything.
Two kinds of failure are never retried automatically, because repeating them cannot help. One is a cloud account that needs reconnecting. The other is a destination folder that has been moved, renamed, or deleted. Both go to "Failed" immediately and wait for you.
A submission that has been "Transferring" for more than 15 minutes with no progress shows "Transfer appears stuck." in its expanded row, with a Retry Transfer button. You don't need to do anything, because EZ File Drop checks for stalled transfers every couple of minutes and restarts them on its own, up to five times. Click Retry Transfer if you want to try right away, for example after reconnecting the account or freeing up storage space.
If all five attempts fail, the submission moves to "Failed" with the message "Transfer stuck: gave up after 5 automatic recovery attempts. Click Retry to try again." The files are still held, so a retry can still deliver them.
Notify on transfer failure is on by default on every form. It emails you once a submission has failed for good, whether it failed immediately or after all its automatic attempts. The subject begins "Action needed:" and names the upload destination.
The form owner is always emailed. To add anyone else, use the To row of that notification on the form's Notifications tab. One email is sent per failure rather than one per attempt, and a submission that fails again after a retry sends a new one. See Set up email notifications.
An "Incomplete" submission sends a separate Partial Upload email that names exactly which files are missing. It goes to the form owner and failure recipients only, never to the uploader.
EZ File Drop does not keep your files. A delivered file is removed about an hour after your cloud storage confirms it arrived, and any file is removed after 30 days whether it was delivered or not.
Those 30 days are your window. While the files are still held, a retry can deliver them. Once they are gone, retrying cannot bring them back, and the uploader has to submit again.
EZ File Drop emails you seven days before that happens, with a subject that begins "Action needed:" and names the form. That email is your last chance to act on the submission.
From that same point, a recovery panel headed "Recover files" appears on the expanded submission, so you can download the files and put them where they belong yourself. It shows for the person who owns the cloud connection the form delivers to, and only after a retry has already been tried at least once.
An upload that was turned away before it was sent never reaches EZ File Drop, so it does not appear on the Submissions tab. One that started but never finished does appear, either as "Failed" with the message "This upload was never completed." or as "Incomplete" if some files made it. If nothing appears, ask the uploader what they saw.
On a free trial there is one more possibility. A trial has a hard upload allowance. Once it is used up, anyone opening one of that team's forms sees "This form's account has reached its trial bandwidth limit. The owner needs to upgrade to a paid plan before more files can be uploaded." Choosing a plan lifts the block, and forms on a paid plan are never blocked this way. See How bandwidth works.
Sending it this way saves you from gathering the details yourself, and it points support to the exact transfer to look at.