Does anybody know what the maximum expiration time for Cache Services in Google Apps Script is? I am running my script on Google Sites and have tried to run a trigger that re-caches the cache, but the cache seems to still expire overnight and I am not certain how long it lasts. If anyone has timed the actual length of the cache it would be good to know - unfortunately, Google hasn't made this info public.
We are working on adding that information to our documentation, but the maximum time something can be stored in the cache in 6 hours (21600 seconds) and the default time is 10 minutes (600 seconds).
Related
No matter what we try, all YouTube API requests we make are failing.
As we first thought this was a propagation issue, we waited out 10 minutes, then 30 minutes, 2 hours and now over 24 hours, to no avail.
We have found this thread, which covers a similar issue with an iOS app, but does not correspond to our use case.
Here is a run-down of what the problem is:
Activating the "Youtube Data API v3" API for our account shows as successful, and the API shows as enabled.
A POST to https://www.googleapis.com/upload/youtube/v3/videos (videos insert) consistently fails with the following error, despite the fact that we have waited hours for the API enabling to propagate:
Access Not Configured. YouTube Data API has not been used in project XXXXXXXXXXXX before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=928939889952 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
Although the error does not directly point to this, our "Queries per day" quota for the YouTube Data API is showing as "0". We are not able to understand why this is showing as zero, and unfortunately, all attempts to edit it to something higher have failed, and disabling and then re-enabling the API has not solved the problem. In a completely separate project/account, this shows as "10,000" when enabling the YouTube Data API, and indeed video insert API calls work under that project.
This is a significant roadblock for us, as it prevents us from deploying our application: any help would be appreciated.
No access configured
Actually means that you dont have permission to access the api. It basically means you have enabled the api but dont have the quota to use it. Its different then the you have run out of quota error message.
After a strange change sometime last year by default the quota for the Youtube api is now 0. You need to request a quota extension it can take anywhere between a week to several months to get permission to use it.
It took me three months. No i dont have any idea how they expect anyone to develop a new application without any quota and to know ahead of time that they need to apply for quota in order to start developing their application. Its quite frustrating.
We have a self-hosted content management system which offers clients the ability to sync data from their GA profile with the content they maintain within the application. So, we're dealing with an arbitrary number of clients who can have an arbitrary number of profiles. Each client is required to simply enter their profile ID and request a token.
The issue we are running into is our Google Developer project is hitting its 50k/day quota pretty quickly, but Google has been unresponsive with our requests to increase this quota. Does anyone have experience with requesting an increase? If so, about how long did it take?
Aside from a quota increase, does anyone have suggestions on how we can avoid this situation?
It can take several weeks to get the quota set up. That is why it is recommended that you keep a check on your quota and request when you hit 80% of max. Only way to avoid it is to tune your requests don't request data you already have again store it in your system. if its an existing customer you should only be requesting the last few days worth of data. Everything else is static and shouldn't change.
How long ago did you request it and how critical is your problem?
I have a Windows Phone Google Tasks app that has been growing in popularity and a couple months ago I realized I was hitting the Google Tasks API courtesy quota of 5,000 daily requests.
I was getting 403 "DailyLimitExceeded". Following the advice of multiple forums, I requested an increase and was eventually granted 20,000 daily requests.. However, it still seems that the 5,000 limit is blocking me. To get around this I have created two more projects and have my app round robin users between them to help balance load.
I am using OAuth so I don't think I'm hitting the anonymous have limits. The projects all list the quota as 20,000 and track towards that but my original project starts erroring right around 5,000.. I have not hit that high of usage on the new projects yet. I have also tried turning off the API and back on, but that didn't help.
Any ideas on how to fix this?
There was a bug in the quota increase process that prevented changes from going into effect. The bug has been fixed in code and should be released early next week.
Session timeouts work perfectly as expected when a clients' local time is in sync with a UTC server, however if the client has their local time set to some time in the future, they constantly receive session timeout messages and are logged out of the site.
What are some possible solutions to this problem used by other developers? I am sure that I am not the first person to have this problem, however I cannot find much information on it online.
Thanks but I worked it out. Before, I was setting a user's session to expire at a certain time, 15 minutes after their last activity. However, that expire date is set based on the UTC server's time, not the user's local time. So when the client's local date/time was compared to the expire date/time it would always cause a timeout for users with local time more than 15 minutes in the future.
I fixed this problem by setting the expire time to be an amount of time (15 minutes) rather than the actual date/time of expiration. That way no matter what the user's local time is, they will timeout 15 minutes after their last activity.
I want to increase the 'session timeout', which currently is set to 20 minutes. How can I increase or decrease it by one hour, or in other terms, 60 minutes?
There are a few ways to accomplish what you need, as we ran into the same issue when doing our NetSuite integration.
You can make a dummy search event every couple of min. We searched for a bogus transaction that we knew would never be created, and limited to a date in the distant past and only that date. That way the search would return very quickly with zero results.
Implement SingleSignOn. This is the preferred method. Once you initiate the single sign on, if the session has timed out on you previously you can quickly make a new session using tokens and do not need to ask the user for their username/password again.
We had a service that needed consumed at two different points in the application that did not know about each other. So the way we got around this but still using one service was saving the cookies from the service in a shared location. Then when the service is needed by one of the application they would recreate the service from the cookies. If the service had timed out we would recreate the service and update the cookies. This method became outdated once we implimented SingleSignOn, as then we could just create the service from the tokens as needed, and the tokens were stored in a shared location.
Hope this helped.
There is no standard way that I know of in NetSuite, you could though use a browser plugin to refresh the page or click the home button every 19 mins. Would work if for example the person is AFK.
There is no way to change the web service request timeout period (for sync operations it lasts approx 15 min, then the operation gets terminated on the server side). The general practice for long running operations that takes more than 15 mins is to use async requests.