# OAuth inactivity deletion warning despite active Shopify Google sign-in — DulChefs

**URL:** <https://discuss.google.dev/t/oauth-inactivity-deletion-warning-despite-active-shopify-google-sign-in-dulchefs/410711>\
**Category:** Compute Infrastructure\
**Tags:** infrastructure-general\
**Created:** [November 3, 2026, 2:57pm UTC](https://discuss.google.dev/t/oauth-inactivity-deletion-warning-despite-active-shopify-google-sign-in-dulchefs/410711 "2026-11-03T14:57:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carlos\_Jimenez](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/carlos_jimenez/32/287115_2.png) [@Carlos\_Jimenez](https://discuss.google.dev/u/Carlos_Jimenez)\
**Post date:** [November 3, 2026, 2:57pm UTC](https://discuss.google.dev/t/oauth-inactivity-deletion-warning-despite-active-shopify-google-sign-in-dulchefs/410711/1 "2026-11-03T14:57:02Z")

</div>

Hello Google team,

On 3 November 2026, we received an automated email stating that OAuth clients in our DulChefs project had been inactive for at least five months and would be deleted in 30 days. However, this connection is used for customer Google sign-in on our production Shopify store.

What we checked:

- Google sign-in is enabled in Shopify, and its configured client ID exactly matches the web OAuth client named DulChefs in the project mentioned in the email.
- Google Cloud Console showed a last-used date of 27 October 2026, which is already inconsistent with five months of inactivity.
- Customers have been using Google sign-in regularly, including reported accesses on 2 November. We have not independently audited each customer login.
- On 3 November, we explicitly signed out of the storefront customer account and completed a fresh sign-in using Continue with Google. It returned successfully to the authenticated DulChefs account.
- We have not deleted or replaced the credential.

Could you please clarify:

1. How can we identify the exact OAuth client affected by the email and verify whether deletion is actually scheduled?
2. Does a successful fresh Google sign-in protect the client from inactivity deletion even if the Console last-used date has not updated yet?
3. Could this be related to stale notification/status reporting, as described in [OAuth clients still flagged for deletion after being updated](https://discuss.google.dev/t/oauth-clients-still-flagged-for-deletion-after-being-updated/388431) ?
4. What official support route is available to confirm the status privately? Our Cloud support plan is Basic, and attempting to create a case reports that we do not have permission.

We can provide the project/client identifiers privately through an official support channel if needed. No client secrets, tokens or customer data are included here. We need to preserve the existing Google sign-in integration without disrupting customer access.

Thank you,  
Carlos Jimenez — DulChefs

---

<div class="post-metadata">

**Author:** ![James\_Auble](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/james_auble/32/287215_2.png) [@James\_Auble](https://discuss.google.dev/u/James_Auble)\
**Post date:** [November 3, 2026, 5:01pm UTC](https://discuss.google.dev/t/oauth-inactivity-deletion-warning-despite-active-shopify-google-sign-in-dulchefs/410711/2 "2026-11-03T17:01:25Z")

</div>

I received a 6 month inactivity warning on an OAuth client today that’s been actively used for the whole period. In the client on google console it even says “Last Used ”.

Per Gemini’s advice I just renamed the client and renamed it back and it now shows “Last Used ”.

Anyone else experiencing this?

Should I just ignore the warning?
