• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Getting errors from Dropbox

Plasmoid

Member
I created a very simple two-step workflow with Dropbox such that:
  1. Triggers when a new file (for me this is an image/video)
  2. Moves the file into another folder
I am running into the issue where I keep getting the same error message:
JSON:
{

    "error_summary": "too_many_write_operations/..",

    "error > reason > .tag": "too_many_write_operations"

}

This is true even when I only upload very few images/videos. My understanding is that Dropbox's API allows for 100's of API requests per minute, if not more. I contacted Dropbox support and told them what is happening because that error message should only be the API response Pabbly receives. However, they insist that the error is coming from within Pabbly Connect.

Here's a copy of the workflow: https://connect.pabbly.com/workflow...fVGkLHwIGUAYIe11TCRtXVF0nA05VLlYTCzhYBgMrVDU#

I've added a delay of 10 minutes in between and some retry behavior to help with the issue, but I don't think such a simple workflow should be getting such errors.
 

Preeti Paryani

Well-known member
Staff member
Hello @Plasmoid,

Could you please provide us with the Task History ID where this error occurred? This will help us investigate the issue more effectively and provide you with the best possible assistance.
 

Plasmoid

Member
Hello @Plasmoid,

Could you please provide us with the Task History ID where this error occurred? This will help us investigate the issue more effectively and provide you with the best possible assistance.
Hello, I have a ton of them, so I'll just provide a few examples:
- https://connect.pabbly.com/task/his...YzMzA0M2M1MjZmNTUzNjUxMzU1MTYwNTQzNDBmMzIi_pc
- https://connect.pabbly.com/task/his...YzMzA0MzM1MjZkNTUzNzUxMzc1MTYwNTQzMTBmMzci_pc
- https://connect.pabbly.com/task/his...YzMzA0MzE1MjY0NTUzMTUxMzQ1MTYxNTQzNzBmMzMi_pc
 
D

Deleted member 15445

Guest
Hey @Plasmoid

We have checked your issue and it appears that the error message that you are getting is not from our end. We do not show the mentioned error "too_many_write_operations/.."

For checking further, we would require the activity logs from Dropbox's end. As you are already in a conversation with them, please convey the same and let us know if you receive any update.
 

Plasmoid

Member
Hey @Plasmoid

We have checked your issue and it appears that the error message that you are getting is not from our end. We do not show the mentioned error "too_many_write_operations/.."

For checking further, we would require the activity logs from Dropbox's end. As you are already in a conversation with them, please convey the same and let us know if you receive any update.

Hello Luv, thanks for checking the issue.

From Dropbox:
If ultimately the developer of this integration suspects this may be an issue on Dropbox's end, please request that they reach out to our developer support here:
http://www.dropbox.com/developer

So they're refusing to provide any support for me at this point, instead they want you guys to contact them.
 

Preeti Paryani

Well-known member
Staff member
Hello @Plasmoid,

This error (too_many_write_operations) originates from Dropbox’s end and is not related to Pabbly Connect. However, our team will reach out to them regarding this issue.

We also recommend that you reach out to Dropbox support directly to help expedite the resolution.
 
Top