Is LUIS limited for use? - botframework

I have been receiving exception in my application saying
Exception: Response status code does not indicate success: 403 (Quota Exceeded).
Does this means we are only allowed 1000 hits per application per month on the LUIS?
Anyother justification are welcomed around this exceptions.

There are several quotas on LUIS's keys usage:
Free key:
5 calls / second
10 000 calls / month
Standard key:
50 calls / second
See Azure portal's capture below where the 5/second is visible for free plan:
And link to LUIS pricing here

There is also (or was) an out of Azure preview key good for only 1000 messages per month on a rolling daily window. Not sure if it’s still there but it could be what you’re running into. It was called the bootstrap key and was just using your programmatic api key as the runtime key.

It is also depending on the starter key that was created for each user when using LUIS free from first time, we need to migrate the luis model to a Azure resource, only then we can use 10,000 message free per month as per F0 plan, else it will be 1000 for each user authorizing key.
Reference link https://learn.microsoft.com/en-us/azure/cognitive-services/luis/luis-concept-keys

Related

Outlook contact folders (Categories) subscription API issue

API Availability? - Is there any APIs to subscribe create contact category resource?
We are currently using the contact folder subscription for that we are facing the below issue.
Issue description - For the create/update contact, we do not receive any notification from Microsoft for graph and graph beta API.
Details used:
Request body: {"notificationUrl":"","expirationDateTime":"2023-27-06T04:15:43Z","resource":"/me/contactFolders/<%contactFolderid%>/contacts","changeType":"created,updated,deleted","clientState":""}
API used - https://graph.microsoft.com/v1.0/subscriptions (Microsoft documentation)
According to the doc maximum length of subscription for contacts resource is 4230 minutes (under 3 days).
Your expirationDateTime=2023-27-06T04:15:43Z is strange. Based on expected format yyyy-MM-ddThh:mm:ssZ you set the month to 27.
Based on this probably only resources /me/contacts or /users/{user_id}/contacts are supported, not /me/contactFolders/<%contactFolderid%>/contacts.
Try to create a subscription with expirationDateTime that doesn't exceed 3 days
{
"notificationUrl":"<your_notification_url>",
"expirationDateTime":"2023-01-28T04:15:43Z",
"resource":"/me/contactFolders/<%contactFolderid%>/contacts",
"changeType":"created,updated,deleted",
"clientState":""
}
If possible in your case you can use delta to periodically get a set of contacts that have been added, deleted, or updated in a specified folder.
GET /me/contactFolders/{id}/contacts/delta
GET /users/{id}/contactFolders/{id}/contacts/delta

Plaid transactions unavailable 2 minutes after a user connects their bank account (PRODUCT_NOT_READY)

I'm currently accessing user's plaid bank transactions using this approach:
User connects to plaid through the plaid web/iframe component
2 minutes later POST /accounts/balance/get is called, which returns a list of bank account ids (account_ids)
The transactions for the bank accounts retrieved in 2. are requested using POST transactions/get
transaction/get then gives the following error: PRODUCT_NOT_READY : the requested product is not yet ready. please provide a webhook or try the request again later
What I'm unclear on is how to trigger plaid to start pulling transactions. The documentation mentions that 30 days of transactions are available after ~10 seconds of "connecting an item to link". Is the user connecting to plaid through the iframe considered connecting to link (since it calls POST /link/item/create)? Ideally I can get access to the transactions without having to use webhooks.
Thanks!
Did you make sure to initialize Link with the transactions product in your call to /link/token/create? That would be the most likely source of the error -- the Item won't start fetching transactions on link unless transactions is specified in the products parameter of the /link/token/create call.

YouTube Data API v3 shows quota 0 out of 0

I'm using YouTube Data API v3 to retrieve a video info (title, description, thumb) when a user pasted the URL into my internal system. I started getting an 403 error about quota.
When I open Console Developers Dashboard, it shows 45 requests in the last 30 days (that system is not used all the time).
When I click to get an overview from that API, under Quotas, my queries per day shows 0 without possibility of change that limit.
I got a message at the top of the page to request more quota limit but when I follow that link the form tells my current limit is 0 and to require a new limit - which is 0! Can't proceed without any number greater than 0.
Does anyone knows if that is a bug?
This is intended behavior see issue #211012781
Hi. If you're seeing Queries per day quota set to 0 and the API is indeed enabled, then this means that your project’s access to YouTube Data API Service has been disabled.
You should’ve received a notice via email regarding this action, which also contains the steps that need to be taken to regain the project’s access. But just in case you missed it, please fill out and submit the exceptions form below:
https://support.google.com/youtube/contact/yt_api_form?hl=en

Is there a limit to the number of calendar events that can be programmatically scheduled for a given user?

My web app has an event scheduling feature, and I'd like to automatically create, update, and delete calendar events from users' individual calendars as the event details change on my site.
My plan to do this is to set up an automated/service user (e.g. events#example.co) and use the Calendar API to send invites that come from that user. As the event gets updated I continue to use the API through that user (using a server-to-server authentication protocol, so no human authorization required) to modify the event and deliver updates
If I'm scheduling several thousand events - will this scale with just one user? It doesn't feel right to schedule so many events under one automated user. But then again, it might work just fine.
Is there a limit to how many events I can schedule?
Is there a more sane way to approach this overall?
Thanks!
The google calendar api applies some standard quota limits on you. Basically the number of requests that you can make. However when you are planing on using a single user then there will be some other rules you will need to consider
Copied from here
If a user has created more than 10,000 events in his or her calendar within a short period of time, that user might lose calendar edit access.
If a user creates more than 25 new calendars within a short period of time, that user's calendar might go into read-only mode.
In order to prevent spamming, Google Calendar limits the number of invitations a user can send to external guests. This limit varies depending on the action, and is usually between 100-300 guests.
You can do this using a service account. To my knowledge there is no limit to the number of events you can put in a calendar per day however as stated above there will be a limit to how many you can insert at once.
I am not aware of a more sane option than this sorry.

In-App Billing subscription issues

With the release of the new subscription option from In-App Billing API we started a proof of concept of the service and we found a few issues. Has anyone else tried it and would have some answers for us? Here's the issues we have been facing so far:
1 – While testing the unsubscribe functionality, the Google Play interface displays a white page with an “Item not found” message and a retry button. Is it due to the fact the app is not yet published? If yes, how can we test this flow without publishing it first?
2 – Inter device synchronization. When making a subscription on one device, other devices tied to the same account did not receive a OnPurchaseStateChange event. Is it again due to the fact the app is not published? Or are subscriptions tied to a particular device and not to an account?
3 – On our Google merchant page, when we cancel a purchase, the device does not receive a notification telling the subscription has been cancelled. Is this a bug? As a workaround we are manually checking the current time and comparing with the expiration date to force a restore transactions call. At this point, we are able to see the subscription is no longer valid. Do you think this is an acceptable solution?
4 – When a subscription is made, two transactions show up on the Google Merchant page: a FAILED transaction with a value of $0 and a valid one with the value we charged. Is this the expected behavior? What’s the purpose of the $0 FAILED transaction?
If anyone has faced similar issues we would like to know. Maybe these could be bugs on Google's end or maybe we did not understand 100% how it is supposed to work.
Thanks in advance.
1.I had the same issue and after I published (and later unpublished) my app I could see the app page in the market,so you can publish and than unpublish.
2.I didn't check it with subscriptions ,but for managed item i didn't get purchaseStateChange on two different devices as expected.
3.I do get subscription expired after canceling one,but only after a while.
I didn't understood how you can get the expiration date ?
you only can get it with access to play developer api.
the restore transactions will give you same purchaseStateChange as you got when purchase the item.
*in the developer guide it is recommanded to use restore transactions only in first app use.
4.I have same issue,and i heard at least about 10 people with same 0$ charge.

Resources