Plasmoid
Member
I created a very simple two-step workflow with Dropbox such that:
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.
- Triggers when a new file (for me this is an image/video)
- Moves the file into another folder
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.