Hi - I have several ZAP’s that have been running fine since I created it several years ago recently began returning an error message and as far as I know nothing on our end has changed, I have reviewed the trouble shooting recommendations and can’t find anything amiss
Here’s the zap
Here’s the error
The directory exists on dropbox and the file attached to the email *is* getting uploaded to Dropbox.so I’m not sure why it’s generating an error
Thanks in advance for any guidance you may have on this
It sounds like you’re getting “File/folder not found” errors on different Dropbox actions (Upload File and File a File). I did come across few cases of that sort of error in the past for folks that had over 4000 files in the connected Dropbox account and I’m wondering if that could be the case here. Can you confirm whether you’ve got over 4000 files in the selected folder or connected Dropbox account?
Looking forward to hearing from you both on this!
Anyone get a fix for this? I'm getting the same
Hi there @HB2024,
I did some digging into our notes, and it seems like affected triggers, actions, and searches now include an optional but default-true "Include Sharing Link" field. This can be explicitly set to False to disable the generation of sharing links, and mitigate any issues caused by the hydrator. Like so:
Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!
Thank you will give that a try and update with details when we have had a few zaps pass through. Its strangely intermittent.
Hi @HB2024,
We just wanted to see how everything is going with your Zap. Did Ken’s recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
We're looking forward to your response.
Yes.. Disabling the sharing link has sorted the errors we were getting. Thank you.
Wow! Thank you for confirming that Ken’s resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.
Hi - I have several ZAP’s that have been running fine since I created it several years ago recently began returning an error message and as far as I know nothing on our end has changed, I have reviewed the trouble shooting recommendations and can’t find anything amiss
Here’s the zap
Here’s the error
The directory exists on dropbox and the file attached to the email *is* getting uploaded to Dropbox.so I’m not sure why it’s generating an error
Thanks in advance for any guidance you may have on this
Doug
Hi there @HB2024,
I did some digging into our notes, and it seems like affected triggers, actions, and searches now include an optional but default-true "Include Sharing Link" field. This can be explicitly set to False to disable the generation of sharing links, and mitigate any issues caused by the hydrator. Like so:
Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!
since I’m facing the same issue, could you please let me know how to do this? Thank you in advance!
Hi @greta_sch
Did you manage to locate the field Ken mentioned?
If not, you’ll want to head over to the Dropbox Upload File action in your Zap. At the very bottom of that action you’ll find the Include sharing link? field which would need to be set to No:
Hope that helps! Let us know if you’re still running into errors after updating that field or if you have any other questions.
Hi @SamB,
I came across this post two weeks ago after receiving the Dropbox “File/Folder not found” error message in multiple zaps. I set the “Include sharing link” to “No” as suggested here.
Yesterday I received the error again:
My Upload to Dropbox settings:
In our process, three files are received simultaneously through three Zaps, and all are uploaded to Dropbox at the same time. In this case, only one of the three Zaps failed:
Hi @DanaB,
You may be experiencing a race condition where multiple Zaps try to access the same Dropbox folder simultaneously, causing a "File/Folder not found" error. To fix this, try adding a delay between Zaps, verifying file paths for accuracy, reconnecting Dropbox to Zapier, and ensuring the connected Dropbox account has the necessary permissions.
If you've tried these steps and you're still encountering the error, please let us know. We're here to help and we'll do our best to get this resolved for you.