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.

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 existinginbound 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.

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.

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.

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.

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.

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.

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.

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

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!