Fixed
Status Update
No update yet.
Comments
gi...@block.xyz
Hi. We are also experiencing the same behavior since several days ago.
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.
If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.
Please advice.
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.
If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.
Please advice.
ro...@kognitivinc.com
Hello,
As the example shown in the video is testing the connection multiple times in a row, has it happened by testing the connection once (or until it succeeds), then running the code and queries needed and after a while trying to connect again? Is it still failing?
Regards.
ma...@gmail.com
hi. it is happening randomly. the user uses the same credentials and same scenario each time.
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.
Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.
Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?
jo...@gmail.com
I have the same problem, since in this last month my script is executed by many users.
It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.
I tell my users to try to run the code over and over again, until they finally connect.
It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.
I tell my users to try to run the code over and over again, until they finally connect.
yu...@expensify.com
Hello,
Thank you for your comments, this has been forwarded internally.
Regards.
jo...@oikos-international.org
Hi Team,
I have the same issue, getting this error "Failed to establish a database connection. Check connection string, username and password." around 30% of the time.
We are getting frequently below error.
Error : Failed to establish a database connection. Check connection string, username and password. at __GS_INTERNAL_top_function_call__.gs:1:8
Please fix this issue ASAP
I have the same issue, getting this error "Failed to establish a database connection. Check connection string, username and password." around 30% of the time.
We are getting frequently below error.
Error : Failed to establish a database connection. Check connection string, username and password. at __GS_INTERNAL_top_function_call__.gs:1:8
Please fix this issue ASAP
jo...@google.com
Hi team,
Our deployment is experiencing the same issues, spiking on August 1 -- by August 4 we realized that our allowlist in Cloud SQL lacked a few critical subnets. That was completely a problem on our end.
After fixing it, the connection error rate dropped to the ambient level of less than 45k/day. On August 12 we tracked only ~3k errors, but after that connection errors have been on the rise again, reaching 125k failed connections just yesterday (Aug 16).
I understand that the issue has already been reported internally. But I hope these additional time references will be helpful.
Thanks
Our deployment is experiencing the same issues, spiking on August 1 -- by August 4 we realized that our allowlist in Cloud SQL lacked a few critical subnets. That was completely a problem on our end.
After fixing it, the connection error rate dropped to the ambient level of less than 45k/day. On August 12 we tracked only ~3k errors, but after that connection errors have been on the rise again, reaching 125k failed connections just yesterday (Aug 16).
I understand that the issue has already been reported internally. But I hope these additional time references will be helpful.
Thanks
ma...@dynamicscreen.com
Hello,
In order to move this investigation forward our product engineering team may need sensitive data, therefore Issue Tracker is not the best environment (public) to do so.
This is why I strongly encourage you to reach out to your admin to open a ticket to
If you have any additional questions, please feel free to reach out.
Kind regards.
[Deleted User] <[Deleted User]>
Comment has been deleted.
[Deleted User] <[Deleted User]>
Hi there, I'm another Enterprise level user with roughly 50 automated Apps Scripts that need to connect via the JCBC. I was not affected by this issue last yet, but now it's precisely as mentioned above. My scripts fail roughly 50 of the time and it seems to be a completely sporadic error. I'm going to go ahead and take the advice above to open a ticket with our Google Admin.
si...@comeen.com
I'm also getting this error increasingly. Many scripts running that normally run without issue but the error rate seems to be increasing by the day
fr...@parkside-interactive.com
I'm also having this issue, and the error rate is increasing with time.
ga...@comeen.com
Hi
Can any one help on this, incase found any solutions
Can any one help on this, incase found any solutions
yu...@pwc.com
We've also experienced an increasing amount of errors. On aug 26, I found that our IP whitelist was outdated so depending on the IP that was used on Google's side the connection might have been failing because of the firewall that was blocking the connection.
A few days ago I've updated the whitelist based on this document:https://www.gstatic.com/ipranges/goog.txt . This has reduced the number of errors drastically. However, it seems that every now and then we still have the same error. Maybe the list provided by Google is outdated and it's using different IP addresses than the ones listed?
A few days ago I've updated the whitelist based on this document:
[Deleted User] <[Deleted User]>
Hi, I am experiencing a heap of sporadic connection errors. My users are based across the United States, meanwhile I am accessing the app from the UK and it seems that I can always connect without issue. It seems like people on the west coast are more likely to experience it than the east coast. Some people reporting the problem are operating from as far east as Texas.
The DB we are connecting to is an AWS RDS database. So far, no signs of trouble with the database itself.
I don't see what I can do to improve the experience (apart from migrating the app). Any insights?
The DB we are connecting to is an AWS RDS database. So far, no signs of trouble with the database itself.
I don't see what I can do to improve the experience (apart from migrating the app). Any insights?
ja...@google.com
We have had this issue as well and has increased recently as previously stated.
One behavior I noticed was when I caught the error in error handling and tried to reconnect in the same code execution it would fail 100% of the time. So my work around ended up writing code that if the execution was from a trigger to create a new trigger to run the code and that seems to work. If the execution was from a menu I would simply alert the user to re-try.
One behavior I noticed was when I caught the error in error handling and tried to reconnect in the same code execution it would fail 100% of the time. So my work around ended up writing code that if the execution was from a trigger to create a new trigger to run the code and that seems to work. If the execution was from a menu I would simply alert the user to re-try.
is...@google.com
lu...@google.com
Hi All,
Please use enabledTLSProtocols=TLSv1.2 instead of useSSL=false, Hope it will work.
Please use enabledTLSProtocols=TLSv1.2 instead of useSSL=false, Hope it will work.
jp...@google.com
jp...@google.com
To the above response, thank you but this did not work for me. It's still about 50/50 with enabledTLSProtocols=TLSv1.2, so there's no noticeable change.
Description
A short description of the request:
With the new feature that was recently rolled out that allows users to specify if they are working from Office/Home/Multiple Locations, it has really made Google Calendar a lot more useful for a hybrid environment.
Our organization would benefit greatly from being able to both see these locations, as well as change them through the API
What is the purpose of this new feature?
To allow API applications to read from, and update a user's work location. We have a companion app for our organization to help us understand who is in the office and who is working remotely.
What existing APIs would this affect?
Calendar API
What existing data does this use?
The user's configured working location settings.