Solving RuntimeError [429] in Dropbox on Make.com
Problem: RuntimeError [429] too many write operations in Dropbox
If you've recently switched over from Integromat to Make.com, you might have encountered a recurring error: "RuntimeError [429] too many write operations" in random Dropbox modules. This error doesn't seem to repeat on a Dropbox module after restarting the same scenario. It's also been observed that this error occurs when there are two or more scenarios running at the same time.
Solution: Sequential Processing and Sleep Function
The error is likely due to hitting a rate limit because Make.com operations can run in parallel. This is great for efficiency, but it increases your chances of hitting a rate limit, especially if your scenario is triggered by a webhook.
To avoid this, you need to create a processing queue on a first scenario and then use a watch module to process your queue sequentially. This should mimic the behavior that you had in Integromat and help avoid the RuntimeError.
If this doesn't work, another workaround is to put the process to sleep for 1 second after each Dropbox execution. This might not be the most elegant solution, and it does cost an additional operation for each Dropbox execution, but it seems to work.
Troubleshooting Tips
- Check if your scenario is triggered by a webhook. If so, try to process your queue sequentially.
- If the error persists, try putting the process to sleep for 1 second after each Dropbox execution.
Summary
In conclusion, the "RuntimeError [429] too many write operations" in Dropbox modules on Make.com can be resolved by processing your queue sequentially or by putting the process to sleep for 1 second after each Dropbox execution. These solutions should help you avoid hitting a rate limit and keep your operations running smoothly.
You do have further questions?
Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.
