Hi,
I have a google drive connected system, I use it in an integration to create folders in google drive.
It works fine, but after a few minutes of inactivity or sign out my account, the authorization is canceled or expires and I have to re-authorize in my concept connected system for my integration to work again.
How can I always leave it active, without the need to authorize it every moment?
Discussion posts and replies are publicly visible
Did you ever resolve this issue? I've had a Google Drive connected system since November 2022 that was working perfectly fine until March 15, 2023. After that date, I have to manually re-authorize the connected system every evening (my process executes nightly to store a document). From my testing, it seems to expire after about an hour and need re-authorization from the Connected System. I did not change anything on Appian nor Google.
Hi Brad, you are not alone. We are experiencing the same issue and we are investigating. If you find a way to solve this, please share it!
Thank you. I suspect it could be on Appian's side. I have posted a support case and will let you know the outcome.
FYI - Appian confirmed that Google changed their authentication token to expire after 1 hour and has caused an issue with Appian storing the token. A request for enhancement has been entered internally at Appian to have this reviewed and fixed.
Great! Thank you.
Lorenzo
Hi Brad, unfortunately the enhancement request has still to be done. Did you apply a workaround to keep on using this connected system? If so could you please advice?
Hi Lorenzo,
Currently, I've added a gateway after the Google Drive smart service to determine if the push to Google Drive was successful. When it is not, I have an administrator task that uses a!authorizationLink to re-authorize. This helps to be able to complete the task when the drive push fails without going through Appian Designer and manually re-authorizing the connected system.
I have also considered trying to do a simple Get from Google drive every 55 minutes or so to keep the authorization active. I have not tried this yet, so I am unsure if it will work. If I implement that solution, I will update you.