Jotform and Dropbox not syncing all files

Hello,

I've had a persistent problem for a few months now. I have Jotform integrated to automatically download all submission documents to my Dropbox. For the majority of the time, this works great. However, I have noticed there are a number of occasions where the files simply do not sync. When I look on the Jotform system, the file is there, but it hasn't be saved to my Dropbox folder. I have not noticed any particular pattern to this problem, as I can even have within a submission that some files are saved, but others are not. Do you have any idea what might be the cause of this, and if there is anything that I can do to fix this problem? Thanks for your time.

Seth Travis

We have not received any reports recently about the DropBox integration. Generally, there is a chance of failing the uploads if the file is greater than 300MB since there is an API limit for uploading the files to DropBox. As I check the files uploaded to the forms, they doesn't appear greater than 300MB.

You may try removing and reintegrating the DropBox to check if that works. Also, please check the storage space available in the DropBox account. Please get back to us if the issue still persists. We will be happy to assist you further. 

Hi Kiran,

I'm just reporting back that the problem seems to be persisting. I had information that was submitted on February 15th not sync with the Dropbox integration.

After your previous response, I tried removing and reintegrating the Dropbox to see if that was the problem. I also made sure that there is plenty of space, and the Dropbox capacity is not quite half full, so I don't think that's the problem. And as you've noticed, all of these files are generally quite small - usually just a few MB's at the maximum.

For now, I will continue to manually double check that the system is syncing properly, and moving the files over when it is not. However, if you have any additional guidance on this problem, I would appreciate your help. Thanks.

Seth

Thank you for the information, Seth. We'll try to do tests as well on our end.

As soon as an instance of such error occurs again, please let us know.