Dropbox Step Results in an Error, But File is Successfully Uploaded
Hi!
My zap first creates a google sheet with some data, then locates the google sheet, and uploads it to Google Drive.
For some reason, my zap ran 3 times, with 2 fails and 1 success. After the run was complete, I see that the file was uploaded to Dropbox just fine, but the spreadsheet had exact same data 3 times, suggesting the automation tried to rerun itself three times, before finally successfully uploading to to Dropbox on the third try.
I’d like to troubleshoot why it error’d out the first 2 times and had a successful third. Here’s the error message I’m seeing and not quite sure what it is!
Thank you!
Page 1 / 1
Hi there @Hello123!
Hmm, if it errored twice before running successfully with nothing changing in terms of what data was being sent to Dropbox I wonder if it might have been down to a temporary issue in connecting with Dropbox’s servers.
Looking at the status page for Dropbox here it appears that they were carrying out some maintenance on the day that the uploads were attempted:
So I’m thinking that the maintenance might have being carried out during the first two attempts but had been finished by the time the third attempt to upload the file was made.
Do you think that could be the case here or are you still seeing similar occurrences of this behaviour?
Hi @SamB ,
Thanks for getting back to me! I’m still seeing the same behavior occur - it happened again on 2/2. I’ve also sent in a support ticket on that specific occurrence but no one’s gotten back to me yet (36+ hours now), would appreciate anything you can do to help look into the specific error!
Hi @Hello123
Check your Zap Runs history details to see the DATA IN/OUT for each Zap steps.
The issue may be that NO file was found in GDrive in Step 8 to then upload in Step 9.
To help us have full context, post screenshots with how your Zap steps are outlined and configured.
Hi @Troy Tessalone thank you!
Yesterday, the Zap executed again, this time it ran 9 times. 8 fails and 1 success. I’m confident that the Google file is found, and the error occurs in the final step of uploading to Dropbox.
Here’s a successful attempt:
Here’s a failed attempt. Note that there is no “data out” at all when it fails
If this is helpful, here’s the Data Out on the successful attempt.
I might also have an additional clue. When I go into edit the zap and test the actual step of “Upload File to Dropbox,” the file is successfully uploaded, but the zap test shows it errored out. The file can be fully opened and has no problems.
This error says “While requesting “dev_method” from Dropbox we ran into an error: File/Folder not found.” - despite the correct file being correctly uploaded to the correct location!
@Hello123
Check the DATA OUT from the GDrive step and post screenshots from the failed Zap Run.
Hi @Troy Tessalone this is the logs and DATA OUT from the Gdrive step before the failed Dropbox upload!