Communication
Expand section | Collapse all & go to top
See Troubleshoot issues in the Google Calendar Help Center.
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: 2019
Description: Under some circumstances, inline images are not shown in autoresponses to email recipients. Gmail displays a missing file icon instead.
Workaround: Users can host canned response images on external hosting providers and include them in the canned response from there.
Solution
- 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 Preferences
Security & Privacy.
- Select Privacy
- 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.
Solution
Solution
To let people record meetings, administrators need to turn on the following services and features:
Meet is unresponsive when using Citrix VDI
Solution
Related topics
Control
Expand section | Collapse all & go to top
For an overview of Admin console tasks, see Use your Admin console.
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 the Alert Center.
Workaround: Use these alternate methods to capture User-reported phishing events:
- Search the Gmail messages log, with the filter 'Event is: User spam classification AND Spam classification is: Phishing.'
- Set up a custom activity rule.
Reported date:31/07/2020
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 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.
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 Apps
When you are inviting unmanaged users to your Workspace organization, the system sends a Google account transfer request email. When users click Transfer account in that email, they are redirected to a page that mentions Workspace Essentials. This occurs regardless of the subscription on your Workspace account. Users can still follow the steps in the page to successfully convert their personal accounts to Workspace accounts.
Due to a missing authorization check, a user with no permissions is able to list and view all organizational units within their Workspace organization. As per the Workspace permission documentation, viewing organizational units is a permission-restricted action.
Prerequisites: You require an account with limited permissions in the Google Admin console. Assigning the Inventory Reporting Admin permission is acceptable. You don't need to use a prebuilt role. You can make a custom one with no permissions attached.
The issue can happen with Google Cloud Directory Sync (GCDS) in 2 situations.
Situation 1
You rename a group email address in Microsoft Active Directory (AD) after the group 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.
Situation 2
The issue happens when:
- Your group email address contains special characters (such as !#$%&'*+/=?^_`).
- The group synced to Google Workspace using a GCDS version earlier than 5.0.20.
- You upgrade 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 email address in Google Groups.
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 Configuration
- 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: 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.
Description: If user migrations fail when using the classic data migration service and you get a 18017 error, it's due to using Workspace as the migration source.
Workaround:
There are two workarounds if you are using the classic data migration service:
You can also circumvent this error by using data migration (New).
Description: If user migrations fail when using the data migration service and you get a 25002 error, it's due to your 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 number of security keys enrolled by a user is displayed in two different sections of the Admin console; however, they are not consistent with each other.
The correct number of security keys enrolled by a user is displayed in the Security section of a user's security page, that is, the number of hardware security keys registered for a user.
If a user uses their phone's built-in security key, this mistakenly adds a value of one to the number of security keys registered for a user in the Security keys enrolled column in the ReportingUser Reports
Security section. You can have only one built-in security key on your account.
Users are no longer able to add their phone as a security key to their Google Account; however, any devices currently set up will continue to work.
Description: View events associated with iOS sessions may be counted twice in this scenario: If a Gmail iOS user opens a message and swipes left on the message to return to the email conversation list, Email Log Search stores two View events for the message:
- one event for the message that was opened
- one event for the next message in the list view of all messages
This occurs from the inbox or from any folder where a user is browsing and opening messages.
Collaboration
Expand section | Collapse all & go to top
See also the Sheets Help Center.
Google Sheet too large to be editedDescription: 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.
Education
See the Google Classroom Help Center.
Can't link multiple teacher accounts in your SIS to one email addressNote: 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 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.
