Obsolete
Status Update
No update yet.
Comments
lb...@gmail.com
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.
vi...@google.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.
vi...@google.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?
Description
I see there is a list of cases that an Activity can be started on its own out of nowhere.
This doesn't help to avoid a behavior that apps will show something and the user won't be able which app showed the Activity.
What I request, is that for all of these cases, since the user does not know which app started the Activity, there should be a notification showing which is the app that we see its current Activity.
It can be a very low priority notification, because it's not urgent at all, but it should be possible to see it, to identify the app in case it's not doing something we expect it to do.