Is there a maximum amount of individual events that can be tracked in one session by Flurry Analytics?
We seem to have a block after 1000 events are logged in a user session - has this been observed elsewhere?
Flurry confirmed there is a limit of 1000 events logged per user session
Related
We have an app that creates MS Graph Subscriptions where a user wishes to 'track' an outlook email conversation. The subscription uses the conversation id of the email to send notifications when an email within the conversation is sent or received.
Once we receive a notification from MS Graph, we then use the message id to get details about the email so we can store it in our CRM.
I am trying to find information on what the limitations/throttling are in regards to this.
I have read the info here and here but neither are very specific. I also raised a GitHub issue with the MS Graphs docs team here but they have not responded.
I really want to know:
Is there a limit for Outlook based Graph subscriptions per user?
Is there a limit to the number of messages that we can retrieve per user?
Is there a limit for Outlook based Graph subscriptions per user?
Yes there is limit. Each user or groupcan requests 10,000 API call in a 10 minute period. It could be same for user and group as
well. You could have a look official document
Is there a limit to the number of messages that we can retrieve per user?
Normally 500 message each user can retrieve but it is customizable. You can customize it up to 1000 for each user.
For more you could have a look official document here
Hope that would help. If you still have any concern feel free to share.
I'm facing intermittently delay with polling email messages via Gmail API from GSuite user's inbox. Those calls origin from automatic jobs and use multiple G-Suite users to disperse the work and avoid reaching Quota limits.
However, there are still delay of at least 3 minutes in reading the email. Investigating message email headers showed neither errors (429) or delay time, nor quota limits are being reached.
I examined the push notification method and I'm limited to use it.
Are limit units calculated according to domain rather than per G-Suite user so I'm indeed reach quota?
What else can cause those delays?
The Gmail API has usage limits per method and per user.
Email sending limits are calculated per user per day, not per domain.
Limit units are calculated from all requests made from your application per day
You can check your quota in the Cloud console, choosing your project and API (in this case Gmail).
In my case, I could clearly see the email inside the 'Sent' folder but the recipient had not got any email, so I knew the limits for using the API had not been crossed. It was spam protection taking a ton of time to figure out if the sent email was spam or not. The most common case would be if your emails are all similar with a link in them. I removed the hyperlink in my template email notification and it started working again without any delay.
I have implemented App Center Push notifications in my Xamarin forms app, with several messaging strategies.
send same message to list of users.
Note
The App Center Push to User feature limits notifications to 100 users and up to a maximum of 1,000 target devices.
In my logic I break the messages into 100 user blocks.
send unique message to each user (1 user/push).
My question is there a rate limit on how many times I can hit API per minute, per hour etc?
When sending the individual custom messages and group messages, if i need to send to 1000 users, that's 1000 or 10 API hits.
Or did I miss a way to do this in documentation?
I believe that closest you can get as of now - is assigning userIds on SDK side, or using install IDs, and then setting up Push campaigns based on batches of those fields, manually.
Refer to those pages for more details:
Install ID
User ID
App Center is retiring Push Notifications. Means this is no longer a concern and different path will have to be taken.
https://devblogs.microsoft.com/appcenter/app-center-mbaas-retirement/
Does anyone know if Azure Bot's Directline call to refresh token is free or will use the messaging quota? The free one has 10,000 messages/month and S1 package is RM$2.10 per 1,000 messages. This is because the token will expire after 30 minutes, and we want to auto refresh it before 30 minutes.
Does anyone know where to check the quota usage of the 10,000 messages?
In the Azure Portal's Web App Bot's Analytic page, it shows the number of activities, not sure if it is same as the 10,000 messages?
Thanks
Each activity is a message. From this page:
Bots communicate with the Bot Service channels by sending Activity
objects to the channel endpoint via HTTP POST, and by Activity objects
being sent to the Bot’s endpoint via HTTP POST. Each of these Activity
POSTs is a message.
No, they do not count. The calls to refresh the token are not activities, therefore not messages.
Yes, the analytics page is the correct place.
Scenario:
We send messages (of same type) to a queue from multiple senders. Each sender will send groups of messages that are tied together by a unique session id for a given group. There is not limit to number of groups. On the consuming side, we have multiple receivers.
Question:
If receivers do not call await session.CloseAsync() on the last message in a group, will there be any performance implications down the road in our instance of azure service bus?
With message sessions, closing a session indicates that any other receiver can pick up the session and continue processing (message sessions can be only processed by a single receiver to ensure FIFO semantics). You should strive to close the session when it's no longer needed or is over. That way your client can start processing messages for another session that is pending processing.
There is a good sample with explanation how sessions work from Clemens you might have a look at as well.