Twitter quota

[jlocatell]

It was a while without this error but with a new flow it appears again.

Its just like it is a not solved problem, isnt it?

Flow ID is 43e4bec2-951e-420b-9732-e8b43afe6196

[kkurni]

The error said that "out of quota".

try to check twitter query again, it probably trigger to broad search query.

[jlocatell]

ok, what I need to understand is how to deal with a quota error. Need to work the twitter query? I think that it is a very specific one bu I could be wrong.

[kkurni]

You can refine the twitter query and check how many times it get triggers by going to activity.

Or clicking on Info symbol of that flows and see how many times it triggered.

CC @sammerch

[kkurni]

CC @SameerCh for more details

[jlocatell]

These are the runs

[kkurni]

#20456374 for tracking

[kkurni]

@jlocatell it seems this flow is fine. but do you have other twitter flow as well ?

It will aggregate the quota with your other flows as well.

[kkurni]

I just confirmed with @SameerCh that the quota is per connections.

So if you have any other flows which use the same twitter connection, you most likely will hit this quotas.

THanks

[kkurni]

Hi @jlocatell

Do you have other flow which use this same twitter connection?

It seems that your twitter connection is hitting 360 call per hour per connection.

Thanks

[jlocatell]

Ideas of workarounds? Thinking in some recurrence but it is a mess to add it to all of the flows that have a twitter action in.

Maybe Flow could add this recurrence to twitter queries automatically? 

only my 2 cents

[kkurni]

Thanks for the idea.

We currently working on this quota issue.

Feel free to submit your idea at our idea forum.

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Thanks

[oleshy]

The same connection (67af3dce-fe5b-4ccf-aad1-65ee-41859c23) was used in two different flows for trigger on new tweet. We have 360 calls limit per connection per hour. Since trigger fires each 15 seconds, total number of calls could be ~ 240 per hour. Two flows (flow names: 6a8c77da-6b11-4dec-ba8d-a194b6c3ea2a and 43e4bec2-951e-420b-9732-e8b43afe6196) reached the limit over the 47 minutes. Therefore the error "Out of quota" appears by design. Possible workaround could be creating separate connections for each flow.

[jlocatell]

Thanks for your response.

Never happened when using another tools as IFTTT i.e. Wondering about if Flow could add a functionality in order to resolve this or if it is a licensing a/o API issue. Add a connection for each flow is a mess.

J