See Troubleshoot issues in the Google Calendar Help Center.
Description: Google Calendar can take up to 48 hours to propagate changes in deeply nested groups to event permissions.
See also Directory Help.
Description: The legacy Contacts UI is no longer integrated into Gmail, but is available at contacts.google.com. As a result, Gmail delegates no longer have access to the delegated contacts manager. To set up delegation in Contacts, see Give another user access to your contacts.
- Delegation will continue to be supported going forward.
- The Contacts UI supports Contacts delegation when accessed in standalone mode.
Description: We’ve identified that some users were dependent on the delegates’ ability to manage Contact groups in the old version of Gmail delegation. This functionality has changed in the new version. Delegates are still able to view, create, and email individual contacts and groups of contacts when in delegated Gmail, but cannot modify or delete contact groups.
As before, access to contacts and contact groups is available via the Contacts Picker by clicking the “To” link in the Gmail “Compose” window. Users who were previously using Gmail delegation to manage other aspects of contacts are encouraged to set up delegation within the Contacts product.
Description: We’ve identified a small number of users who unexpectedly see one of these alerts regarding their profile photo:
- A prompt to "Choose a single profile picture" in https://myaccount.google.com/personal-info
- A warning in Gmail on the web that their "Mail picture may not be visible in all Google products"
Google Workspace administrators cannot retrieve affected users’ profile pictures using the Google Workspace Admin SDK Directory API.
See Fix a problem in the Gmail Help Center.
Reported date: 08/22/2018
Description:Video previews aren’t working in Gmail.
Workaround: Users need to download the video attachment and play the downloaded attachment.
Reported date: 09/11/2018
Description: Contacts delegate access was formerly granted implicitly in some scenarios, when the users were creating delegates with Classic Gmail UI. With the launch of the new Gmail UI however, contacts delegation must be explicitly granted by users. This change in product behavior has happened for security reasons.
See the Google Groups Help Center.
- Unmute your device.
- Go to your device system settings.
- Make sure your microphone is turned on.
- Unmute yourself in Meet: At the bottom of the screen, click Unmute .
Note: Other people can mute you, but can’t unmute you.
On computers using Mojave version 10.14 or later, let Chrome Browser and Firefox access your computer’s microphone using the privacy settings.
Go to System PreferencesSecurity & Privacy.
- Select PrivacyMicrophone.
- Next to Google Chrome or Firefox, check the box.
- In a Chrome Browser tab, enter chrome://restart to restart Chrome and reset all Chrome apps and extensions.
- Restart your computer.
Learn more about additional options to unmute your computer.
To let people record meetings, administrators need to turn on the following services and features:
For an overview of Admin console tasks, see Use your Admin console.
INTERNAL ONLY: The bug number for this issue is b/265618022.
Description: In the Admin Console, there’s a problem when you update multiple users with a CSV file. This is due to a known internal License Management issue. This occurs when you are both using the New Licenses [UPLOAD ONLY] column and including more than 5 users in the CSV file. The upload then fails and the system does not update users' license assignments.
- Try using automatic licensing; go to see About automatic licensing for organizational units.
- Update or create users individually using the Admin Console UI.
- Update or create users with the Enterprise License Manager APIs; go to Method: licenseAssignments.update .
- Update or create users with the GAM command line tool; go to see Updating a License for Users.
If you’re unfamiliar with GAM and would like to know how to set it up, see Use a third-party tool for quick mass provisioning.
Data Export provides export functionality for Google Workspace Core Services. However, the export might not include everything you'd expect. In this case, certain data must be exported through alternative means, as available.
The only currently known limitation is that in a filtered Data Export, only service data owned by users is exported. Learn more about what data isn't exported in a filtered Data Export.
Please contact Google Cloud Support for further clarification or assistance.
Description: When you are inviting unmanaged users to your Google Workspace organization, the system sends a Google account transfer request email. When users click Transfer account in that email, they will be redirected to a page that mentions Google Workspace Essentials. This occurs regardless of the subscription on their Google Workspace account. Users can still follow the steps in the page to successfully convert their personal accounts to Google Workspace accounts.
Description: If a Data region is selected (set to an option other than 'No preference'), then the 'User-reported phishing' alert may not trigger in Alert Center.
Workaround: Use these alternate methods to capture User-reported phishing events:
Description: For advanced content matches, Content Compliance rules with regular expressions sometimes don’t match on .xls files. This issue may sometimes affect some other file types such as .csv.
Description: The Admin console prevents Google Workspace account deletion when there is still active usage of Cloud resources (projects, folders, etc.) associated with that account.
Note: Before deleting projects, reach out to their owners as they might be running your user’s or an external client’s applications. Deleting projects can lead to client app production failure on the Google Cloud project on which the app is running.
Workaround: Before deleting a Google Workspace account, the super admin must first delete all associated Google Cloud projects and folders. If you want to find resources associated with your Cloud organization, go to Google Cloud. The super admin will need the Organization Administrator, Folder Admin and Project Deleter Role to modify project and folder resources.
If your Cloud organization has Apps Script Projects, you need to delete them along with other Cloud projects before you can delete the Google Workspace account. For details, see Get a list of Apps Script Google Cloud projects
If your Cloud organization has Access Context Manager policies defined, you need to also delete them before you can delete the Google Workspace account.
If you would like a programmatic way to interact with your Organization’s resources, see this script found in our open source Github repository.
Reported date: 09/03/2018
Description: You might see a blank window when trying to manage shared drives.
Manage shared drive users in the Admin console > Apps > G Suite > Drive and Docs > Manage shared drives (subject to edition availability).
Workaround: Make sure the admin has a Google Workspace license that includes shared drives. Ensure the Drive and Docs service is enabled.
Description: Your users may see the Google Vault icon in App Launcher, even when Vault isn't included in your Google Workspace edition. In these cases, your account isn't charged for Vault, and users who click the icon will see a page explaining that they don't have access to the service.
Description: When multiple admins are working at the same time on the same settings page, or when the same admin is updating a setting across multiple tabs, updates to settings can overwrite each other with no warning to the admin.
For list settings (such as AppsGoogle WorkspaceSettings for GmailRoutingEmail forwarding using recipient address map), data entered in one tab can be lost if the list is simultaneously updated in another tab.
The issue is seen with Google Cloud Directory Sync (GCDS) in 2 possible situations.
Description: You rename a group email address in Active Directory (AD) after the group has already synced to Google Workspace. Following a sync, GCDS deletes the current group and creates a new group with the new email address.
Workaround 1: Don't change the group email address in AD.
Workaround 2: Manually change the group email address in both AD and Google Workspace so that they match.
Description: The issue is seen when:
- You have a group email address that contains special characters (such as !#$%&'*+/=?^_`).
- The group was synced to Google Workspace using a GCDS version earlier than 5.0.20.
- You upgrade your GCDS to version 5.0.20 or later.
- Following a sync, GCDS tries to delete the group and create it again using the special characters.
Workaround 1: Remove the special characters from the AD group email address.
Workaround 2: Add the special characters to the Google Group email address.
Description: The issue is seen with Google Cloud Directory Sync (GCDS) version 5.0.22 when you complete the following steps:
- In Configuration Manager, click Google Domain ConfigurationExclusion Rules.
- For Users Search Query, enter a user's search query and save the configuration file.
- Delete the same query and save the configuration file.
- Compare the configuration file in step 2 with the file in step 3.
The configuration file is the same. The deleted query wasn't saved to the file.
Workaround: Open the configuration file and manually delete the <usersSearchQuery> setting.
Description: If user migrations fail when using the data migration service and you get a 25002 error, it's due to your Google Workspace for Education Fundamentals edition.
Workaround: In the destination account, put the users into an organizational unit and set the age label of the organizational unit to All users are 18 or older. Then, try the migration again. For details, go to Control access to Google services by age.
Description: The issue is seen with Google Cloud Directory Sync (GCDS). If you change a user's primary email on the LDAP server, the rename isn't taken into account when GCDS syncs the user's license. GCDS tries to add the license to the renamed user and you get a 412 error.
See the known issues for device management.
See also Use Google Workspace on mobile devices.Security
Half-enrolled 2SV state
INTERNAL ONLY: The bug number for this issue is b/284288391.
Description: When 2-Step Verification (2SV) is enforced, users who have not completed the 2SV enrollment process, but have added 2-Factor Authentication (2FA) information to their account, such as a security key or phone number, will be able to sign in using this information.
The status of the half-enrolled users shows in the Admin console as Not enrolled, even though they need to pass a 2FA challenge every time they sign in. To see this in the Admin console, go to ReportingUser ReportsSecurity and check the status of the 2-Step verification enrollment column.
User flow that demonstrates the issue
For a user who is already using their account on a phone
- The user goes to enroll in 2SV.
- For Google Prompt, they click Choose another option, and select Text message or voice call.
- They enter a phone number to receive a verification code.
- Once the user enters the code, a confirmation screen asks them if they want to turn on 2SV.
- If the user does not click Turn On, they remain in the half-enrolled state.
2SV settings for a half-enrolled user
Prompt after logging in
Here is what happens for this user from now on:
Until the enforcement period expires, the user continues to get a prompt to enroll in 2SV (see the following screenshot).
After the expiration of the enforcement period, the user will get challenged for a 2SV on the verified number. After successful login, the user is still prompted to enroll. This might be confusing, but might prompt some users to complete the enrollment process.
If the user selects remember this computer during enrollment, the requests to enroll don’t appear until the enforcement period expires.
See also the Google Drive Help Center.Drive for desktop (formerly Drive File Stream) known issues
For known issues in Drive for desktop, go to the dedicated known issues page here.
Description: The OS X operating system identifies a group of files in a directory as a "package," although the package will appear as a single file when viewed in Finder or other OSX tools. Other operating systems like Windows and Linux do not support this type of package directory, and, currently, neither does Drive.
Workaround: While the files will appear as folders in Drive, they will display normally once opened.
See the Docs Help Center.
See the Forms Help Center.
See the Google Keep Help Center.
See also the Sheets Help Center.Google Sheet too large to be edited
Description: In very rare circumstances, a Google Sheet may grow too large to be edited and will be forced into read-only mode.
Workaround: While the document is permanently in read-only mode, individual tabs can usually be copied out. To do this, right-click on the tab, go to Copy toNew spreadsheet to create the new sheet. Another approach you can take is to download the spreadsheet or copy and paste information from the spreadsheet into a new document.
Description: In Google Sheets, importrange is a way to circumvent the "Disable options to download, print, and copy for commenters and viewers" option.
Workaround: No workaround at this time.
Description: In Google Sheets, importrange counts the sheet being shared against the maximum sharing limit allowed for documents, even though it's only sharing information with another document.
Workaround: No workaround at this time.
Description: In very rare circumstances, a cell's data may disappear from the current version of a sheet.
Workaround: You can recover the missing data by viewing the cell's edit history.
See the Google Sites Help Center.
Description: Google Sites can take up to 48 hours to propagate changes in deeply nested groups to access permissions.
Description: Google Workspace for Education users get an Unable to play video message and error 150 or 151 instead of an embedded YouTube video.
Some YouTube videos can't be played in the embedded player in Google Slides. We are working to provide a more detailed message for users.
Error 150: This error is due to copyright issues, restrictions the content creator has placed on the video, or because the YouTube Player for Education does not allow music videos.
Workaround: Open the video directly in YouTube.com.
Error 151: This error occurs because YouTube Player for Education enforces content-filtering restrictions set on the user's account. Depending on the restrictions, the user might be prohibited from watching certain videos.
Workaround: You need to change the restrictions for the user or organizational unit. For details, go to Give certain users unrestricted YouTube access.
See the Google Classroom Help Center.Can't link multiple teacher accounts in your SIS to one email address
Note: This does not apply to Skyward SMS 2.0.
Teachers receive a 502 error when downloading grades for large classes
with more than 100 stream items and 100 students.
Students can’t preview Drive files on mobile if the download, print, and copy setting is disabled
Orphaned classes occur when a primary teacher account is deleted
Description: After a primary teacher's account is deleted, classes can't be transferred to a co-teacher.
Workaround: No workaround at this time.
How we define a Known Issue
We work on isolating and fixing every product issue that we're aware of. Some issues might not be listed here. We characterize known Issues as follows:
- We can consistently reproduce an unexpected behavior.
- Engineers are actively working towards a fix to correct the behavior.
- The issue is observed globally and has generated a large number of support cases.
What's not a Known Issue
- Product outages: Up-to-date outage information is posted within the Google Workspace Status Dashboard.
- Feature Ideas: We'd love to hear your thoughts! Go ahead and file a Feature Idea.
- Low impact issues: We're also working to fix low impact issues but might not list them here. If you think you might be impacted by an issue that's not listed here, you can contact us.
What to expect from a Known Issue
We intend to fix every issue listed in Known Issues. However, we can't guarantee timelines. In the meantime, we'll add available workarounds as we discover them. For questions or comments, contact us.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.