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
Thanks for the idea.
We currently working on this quota issue.
Feel free to submit your idea at our idea forum.
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.
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.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!