Can you please add some more detail about your flow, Which operartion you are trying to use?
Twitter has very agresive rate limit for some of the operations. You might be using some low rate limit and operation and getting into this issue.
Excellent info about rate limits.
I'm running the same action with IFTTT without problems but interested to do the same with Flow.
I need some ideas about how to deal with these limits via actions/connections.
Sorry for the issue you are facing. Could you please share the flow id for your flow. When you open the flow, the browser url would look like - https://flow.microsoft.com/manage/flows/f64ed9c6-5541-440a-a6e1-7bae7ab2f6e7
The Highlighted part is the flow id.
I will pull up the information about your flow and would be able to help you further.
You are hitting the throttling limit from our system. We have deliberately kept lower throttling limits for twitter connector.
Twitter throttling limits are per user account (not per query). Since users can use the same twitter account in multiple connection so we had to keep lower throttling limits from what twitter enforces.
Yes, I'm running more that one flow using the twitter connection.
I wonder about a workaround at least. Interested in run flows as IFTTT recipes where (at least until now) there are not throttling restrictions.
Or to mimic the IFTTT recipes behavior, the one-flow-only-to-twitter isnt solution in my case.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Find your favorite faces from the community presenting at the Power Platform Community Conference!
Check out the announcement of Power Platform content at Microsoft Ignite!
Features releasing from October 2020 through March 2021