Google Apps Known Issues

Domain Administration & Billing Known Issues

  Administration
Admins can't use Google for Work Support Center or Google for Work Connect
This issue only pertains to Google for Work Domain admins with access to Google for Work Connect or Google for Work Support Center.

Description: On 2015-06-17, between 09:20am PT and 11:00am PT, a subset of users noticed errors while accessing Google for Work Connect or Google for Work Support Center. We are currently investigating this occurrence and will update here as soon as the issue is solved.

Workaround: You can still contact support via the channels listed at How to contact Google Apps support.

Status: Solved - All users should now be able to use Google for Work Connect and Google for Work Support Center correctly.

Missing inbound mail gateway settings
This issue only pertains to domains using the inbound mail gateway settings.

Description: A small portion of Google Apps customers who changed any of their domain-wide email settings in the Admin console between 6:06 am and 5:30pm UTC-7 (US Pacific Daylight Time) on March 24th, 2015 may have noticed that their existing inbound mail gateway settings were removed.

Workaround: This issue has been resolved as of March 24th, 2015. If you have not made any subsequent changes to your domain's email settings, we've already restored your existing inbound mail gateway settings. If you have made any subsequent changes to your settings, we have not restored your existing inbound gateway settings from before March 24th, as we don't want to override any new inbound settings you may have made while restoring them manually.

If you're a domain administrator, please check your inbound gateway settings to confirm that they're correct.

Changes to SSO settings may take 24 hours to propagate

Description: Changes to any one of the following SSO settings may take up to 24 hours to propagate.

  • Enabling/disabling SSO or editing SSO settings for the domain
  • Renaming a user's primary email address, resulting in users not being redirected to SSO for up to 24 hours
  • Changing user Super Admin status, resulting in affected user not bypassing or redirecting to SSO correctly for up to 24 hours

Workaround: After 24 hours have passed, settings and user changes will propagate correctly.

  Billing

Product Known Issues

  Gmail & Groups

Can't find what you're looking for? Check out the Gmail Known Issues to see a comprehensive list.

Email Log Search Errors for certain users querying 4/23/2015

Description: A small subset of users may experience errors when conducting an email log search specifically for 4/23/2015.

Workaround: Do not include 4/23/2015 in the log search timeframe.

Particular messages sent from April 8th to April 24th may appear as duplicates

Description: Between April 8th and April 24th, an issue affecting Google mail servers caused delivery issues to a very small subset of email messages sent to Google accounts. As a corrective measure, the Gmail team decided to re-deliver any potential affected messages. If you had already received a particular message before it was re-delivered, the re-delivered message will appear as a duplicate in your mailbox .

Workaround: The re-delivery tasks started on May 11th, and our engineers have stopped them today. Your domain may have received duplicate messages in the meantime. We are currently investigating the impact of this occurrence and we'll keep you updated regarding next steps.

  Calendar

Can't find what you're looking for? Check out the Calendar Known Issues to see a comprehensive list.

  Drive

Can't find what you're looking for? Check out the Drive Known Issues to see a comprehensive list.

"Google Drive was unable to load your items. Please refresh to try again" when visiting the Old Drive UI

Description: Some users are receiving the error "Google Drive was unable to load your items. Please refresh to try again" when visiting the Old Drive UI 

Workaround: Navigate to the New UI by following these steps

  1. Sign into Drive at drive.google.com.
  2. Click the settings icon in the top right.
  3. Choose "Experience the new Drive"

 

Templates not listed after submitting to the gallery

Description: Users trying to submit the same document as a new template will receive a message stating the template already exists. 

Workaround: Create a copy of the document, set it's visibility setting to either People at <your domain> can find and access or a more public option, and submit the copied document to the gallery.

Non-embedded fonts in non-English .PDF files are dropped after uploading to Drive

Description: If you upload a non-English .PDF with non-embedded fonts to Drive, the words using the non-embedded font will not render properly.

Workaround: Please embed the fonts that are not rendered and re-upload the file to Drive.

Packaged Keynote, Pages, and Omnigraffle files show up as folders in Drive

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.

The storage quota for Apps Unlimited customers is displayed as 10 TB
If you have 4 or fewer users in your organization, each user gets 1 TB of storage.

Description: The Drive storage quota for Apps Unlimited customers is displayed as 10 TB even though Apps Unlimited customers have unlimited storage.

Workaround: This issue does not affect the unlimited storage Apps Unlimited customers are provided with and only affects the storage display value within the Drive interface.

  Google+

Can't find what you're looking for? Check out the Google+ Known Issues to see a comprehensive list.

  Hangouts

Can't find what you're looking for? Check out the Hangouts Known Issues to see a comprehensive list.

Hangouts displays "This party is over" within recurring meeting calendar events for external users

Description: When there are multiple Calendar events with the same Hangouts video call link attached, the call will be available only to the external invitees of the first call. If an external user is invited to a named Hangout, but he was not invited to the previous call, the message "This party is over" will be displayed.

Workaround: Use a new meeting name when the list of invitees is different from the first meeting instance.

The warning explaining that you're chatting outside of your domain does not work if contact sharing is disabled

Description: If you'd like your users to be warned before they begin chatting with someone outside of your domain, you must enable Contact sharing. Currently, the Admin console allows the warning policy to be enabled even when contact sharing is disabled.

Workaround: Manually turn on contact sharing or manually disable warning when chatting outside of your domain. We are currently working on a solution to automatically disable the chat outside of the domain warning policy whenever contact sharing has been turned off.

Hangouts for iOS requires that the Google Photos service be enabled to share photos via the app.

Description: We are in the process of changing the requirement for photo sharing in Hangouts chat from Google+ service to Google Photos. Hangouts chat for Android, Chrome and the web do not yet support the updated switch to Google Photos service with respect to photo sharing. iOS devices already respect this change and only require the Google Photos service to be enabled for photo sharing.

Workaround: Going forward, please turn on the Google Photos or Google+ services in the Apps section of the Google Admin console to allow users to share photos in Hangouts chat.

  Sync & Mobile
Sending large attachments from Outlook 2010 results in an error
This issue only affects users of the Google Apps Sync for Microsoft Outlook tool.

Description: By default, Microsoft Outlook 2010 does not allow sending attachments greater than 20 megabytes (MB) in size. If you try to send a larger attachment, you'll receive an error and the message won't be sent.

Workaround: If you're using Outlook 2010 with Google Apps Sync for Microsoft Outlook and want to send attachments up to 25MB (rather than just 20MB), you can modify your Windows registry as described in this Microsoft article.

Sending .eml and .msg email attachments from Outlook results in incomplete attachments
This issue only affects users of the Google Apps Sync for Microsoft Outlook tool.

Description: Google Apps Sync for Microsoft Outlook users sending email attachments (.msg or .eml) to Microsoft Outlook users hosted on a legacy Exchange environment may receive an incomplete or missing attachment.

Workaround: When attaching an email message as an Outlook item select Insert as Text Only. This will copy the message attachment as text to the body of the new email.

GADS versions 4.0 and higher no longer use the Employee ID field for User Profiles
This issue only affects users of the Google Apps Directory Sync tool.

Description: In GADS versions 3.2.1 and lower, the Employee ID field was used to sync an employee's ID number in your LDAP directory to Google Apps. GADS 4.0+ now syncs employee ID's to a field named Organization ID in Google Apps.

Workaround: If you used previous versions of GADS and are running version 4.0+ for the first time, all of the User Profiles in your sync will be updated to use the Organization ID field. The Employee ID values for all of the User Profiles in your domain that were synced using GADS 3.2.1 will remain unchanged, and future GADS 4.0+ syncs will not update the values. If you'd like to remove the Employee IDs, you can do so using the Directory API.

GAMME returning 503 errors for mail migrations with suspended source users
This issue only affects users of the Google Apps Migration for Microsoft Exchange tool.

Description: During a GAMME mail migration, if the source user is suspended a 503 error will be returned with the message 'Service unavailable. Please try again'.

Workaround: If possible, unsuspend the source mail user.

How we define a Known Issue

We work on isolating and fixing every product issue that we're aware of, some of which may not but listed here. Known Issues are characterized by the following:

  • 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 Apps Status Dashboard.
  • Feature requests: We'd love to hear your thoughts! Go ahead and file a feature request.
  • Low impact issues: We're working to fix low impact issues as well as Known Issues. If you suspect you're impacted by an issue that's not listed here and want to talk to a member of our team, please contact us!

What to expect from a Known Issue

Every issue listed in our Known Issues will be fixed. We can't guarantee any timelines, however, so please be patient. If necessary, we'll add any available workarounds as we discover them. If you have questions, comments, or concerns (or funny jokes), please contact us!