# Google SSO Issues

**URL:** <https://community.weweb.io/t/google-sso-issues/16920>\
**Category:** Ask us anything\
**Tags:** authentication, xano, weweb\
**Created:** [February 27, 2025, 9:45pm UTC](https://community.weweb.io/t/google-sso-issues/16920 "2025-02-27T21:45:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elenagblanco](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/elenagblanco/32/12739_2.png) [@elenagblanco](https://community.weweb.io/u/elenagblanco)\
**Post date:** [February 27, 2025, 9:45pm UTC](https://community.weweb.io/t/google-sso-issues/16920/1 "2025-02-27T21:45:04Z")

</div>

I have been banging my hed against the wall for days now - I am trying to implement the Google SSO and running into strange issue

I am calling the **/oauth/google/init** and receiving the code back, once the code is received I am calling the **/oauth/google/continue**  
through a **Workflow** that passes the CODE and the redirect URI (properly registered as Authorized redirect URIs) to the API

The debugger show the workflow being triggered BUT I do not see any equivalent call on the XANO side

Here is the squence of screens

 ![screen1](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/8efc241bab9df9c29be26c758210f5ab3d5b1017.png)  
 ![screen2](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/c/c772449359497eb577ebbc9118a12ab7a9a50278.png)  
 ![screen3](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/3/391966e65cc0a823e6b7df64a8835f6b4381f7dc.png)  
 ![screen4](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/c/c48dbc5bff168e5ee70d509ea15507a96a167c87.png)

If I run the worflow manually right after having recevied the call, then the API call hits XANO

 ![screen5](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/b/be39b88aa6c2ce7e31f52d4daf14333e4455f09f.png)

Can anybody offer their two cents of why this is happening?

Thank you

Elena

---

<div class="post-metadata">

**Author:** ![elenagblanco](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/elenagblanco/32/12739_2.png) [@elenagblanco](https://community.weweb.io/u/elenagblanco)\
**Post date:** [February 27, 2025, 10:32pm UTC](https://community.weweb.io/t/google-sso-issues/16920/2 "2025-02-27T22:32:21Z")

</div>

Ok - out of desperation I added a DELAY prior calling the **/oauth/google/continue** and the call hits XANO NOW!!! And it works beautifully

I am wondering

 ![screen6](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/d/d8d79fcc1d869bc18397bd3097a9598211a35878.png)  
 ![screen7](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/9/9bcbc15ef8e6e6e5e2f36301b8ada8e90f86a5d9.png)  
if anybody has had this issue? Also this solution seems VERY precarious - @WeWeb - any thoughts??

Attached screens for proof

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [March 4, 2025, 4:17pm UTC](https://community.weweb.io/t/google-sso-issues/16920/3 "2025-03-04T16:17:11Z")

</div>

Interesting! Thanks for sharing the tip. I don’t see the delay you added in your second screenshot. Would you mind sharing where you added the delay? Is it after the “Setting value for `code`” action in the previous workflow?