Today’s blog is all about the error – “Out of call volume quota” Wondering what did I break now? How did I get it? What is the root cause? And the solution, this blog is all about that.
Let me give you some background –
I was checking how my flows were doing via “Run history”. You can also check yours by clicking on three ellipses on any of your flows. Then click on Run history as highlighted below screenshot.
Note – Flow keeps a 28-day run history for you to check for any errors or past runs.
And the flow history turned out to be weird, it was Success, but it failed most of the time! (And I promise I did not break anything yet!)
So I clicked on one of the runs to check what happened and it was weird. My RSS feed flow and helps me keep up to date with the information I require. LinkedIn looks fine, but Twitter was crying.
I went ahead and checked the issue with the Twitter connector. And it says –
“message”: “Out of call volume quota. Quota will be replenished in 00:03:06.”
The error details told me the action – Post a new tweet failed along with the error description.
Root cause & solution –
The reason for the message is you are hitting your API limits of Twitter connector & you can have a look at this documentation – https://developer.twitter.com/en/docs/rate-limits
Also, there is a thread on the community which also explains API limits related to your subscription.
To avoid the issue from recurring, you could –
- Update the recurring frequency – like it can run every 15 or 30 min (depending upon the need)
- Change the trigger, if possible
- Use conditions or Boolean value or flag values (yes/no)
There could be many more scenarios, but I have listed some of them.
The primary reason I was getting this error is that my flow was off for a while. As soon as I turned it on, all the past RSS came thru in a run.
Hope this helps!
Keep reading, keep enjoying, keep exploring!