Hello Google Cloud Community,
I am seeking advice and potential assistance regarding a prolonged OAuth verification process for our Google Workspace Add-on. This add-on is crucial for a key client project, and the delays are now causing significant business impact, including the risk of losing the client.
Timeline:
31st October 2025: Initial request submitted to Google for add-on listing on the Google Workspace Marketplace.
1st November 2025: Received first feedback to update manifest file configurations and to initiate a OAuth verification sensitive and restricted OAuth scopes.
3rd November 2025: Initiate add-on submission for OAuth verification for sensitive and restricted OAuth scopes.
6th November 2025:Received first feedback from OAuth verification team to update instructions to navigate into OAuth consent screen. Team provided instruction on the same date.
8th November 2025: Received another feedback to update demo video with end to end work flow.
11th November 2025: Team shared an updated demo video.
11th November 2025: Received a feedback from OAuth verification team, asking justification for using Drive API scopes. Team provided justification to use drive scope on the same date.
11th November 2025: Google OAuth team suggested to use Picker API instead of drive scope team used.
17th November 2025: Team tried out suggested API, but it was not working with Add-On. Team replied with error details to the google.
19th November 2025: Team followed up with the Google.
21st November 2025: Google OAuth verification team replied informing that they are still reviewing the request.
25th November 2025: Google OAuth verification team replied informing that request is still in their review queue.
1st December 2025: As the approval is delaying team refactored the drive browsing feature kept only least required drive scopes to speed up the approval and replied back.
1st December 2025: Google OAuth verification team replied back informing that there are delays in processing due to high volume of submissions.
5th December 2025: Google OAuth verification team replied back informing that there are delays in processing due to high volume of submissions.
9th December 2025: Google OAuth verification team replied back informing that they are performing a comprehensive assessment to ensure our application's use of requested scopes are aligns with all Google API Services User Data Policies. Some times that process require longer-than-usual processing time.
14th December 2025: Google OAuth team again requested justifications for all the auth scopes we are requesting for their review.
15th December 2025: Team replied back with providing detailed justifications for all the auth scopes we are requesting from Google for the add-on.
16th December 2025: Team sent another follow-up message to Google OAuth team asking to expedite the process as our delivery milestones have already been passed.
From 16th onwards we keep on receiving generic "still under active review" emails (five), with no specific feedback or timeline provided.
Current Situation:
We are still awaiting any specific feedback or a timeline from the verification team. The add-on remains in active review.
We fully understand and respect Google's commitment to security and thorough review. However, a verification process extending over four weeks without specific feedback or an estimated completion date is severely impacting our ability to deliver on critical client commitments.
Questions for the Community/Google Representatives:
-
Has anyone else experienced such extended delays with OAuth verification for Google Workspace Add-ons recently?
-
Are there any alternative (perhaps undocumented) escalation paths for business-critical issues where client retention is at risk, especially when standard support channels (due to our Basic support plan) are limited for technical queries?
-
Could any Google representatives monitoring this forum offer guidance on how to expedite this review or provide a realistic timeline?
Any advice or insights would be greatly appreciated. Thank you for your time.
