#Google Chat Related Codes

#GC-ChatFileDownloadFailed

Issue:

The object failed in the migration with the following error:

• GC-ChatFileDownloadFailed

Details:

An unexpected error occurred while downloading the file from the source. For example, network issues, Google API limitations, etc.

Recommendations:

Try running an incremental or "Retry error objects" migration job later to resolve this issue.

#GC-ChatFileDownloadTimeout

Issue:

The object failed in the migration with the following error:

• GC-ChatFileDownloadTimeout

Details:

Timed out while downloading the file from the source.

Recommendations:

Run an incremental or "Retry error objects" migration job later to resolve this issue.

#GC-ChatFileFolderUnsupported

Issue:

The object failed in the migration with the following error:

• GC-ChatFileFolderUnsupported

Details:

Containers are not supported in the migration.

#GC-ChatFileNotFound

Issue:

The file failed in the migration with the following error:

• GC-ChatFileNotFound

Details:

The error may occur in the following situations:

• Situation 1: The file does not exist in the source tenant.

• Situation 2: Both the source message sender and the migration user (the source user configured in the migration mapping) cannot access the file. In this case, the file cannot be migrated.

Recommendations:

For situation 1, check to make sure the file exists and run an incremental job to resolve this issue.

For situation 2, make sure the message sender or the migration user can access the file. Then, run an incremental job to resolve this issue.

#GC-ChatFilePermissionDenied

Issue:

The object failed in the migration with the following error:

• GC-ChatFilePermissionDenied

Details:

The error may occur in the following situations:

• Situation 1: The source message sender or migration user (the source user configured in the migration mapping) does not have sufficient permissions to download the file.

• Situation 2: The source file cannot be accessed since the Google Drive has been blocked.

Recommendations:

For situation 1, make sure the source message sender or migration user have permission to download the file. Then, rerun the migration job.

For situation 2, check to make sure the source file can be accessed and then rerun the migration job.

#GC-ChatFileSecurityUserMappingFailed

Issue:

The file has been migrated but has the following error:

• GC-ChatFileSecurityUserMappingFailed

Details:

Failed to map the permission users of the file since user mappings are not configured.

Recommendations:

Configure user mappings to map source permission users to destination existing users. Then rerun an incremental or "Retry error objects" migration job.

#GC-ChatFileTrashed

Issue:

The file failed in the migration with the following error:

• GC-ChatFileTrashed

Details:

The file has been deleted from the source.

Recommendations:

Make sure the file exists in the source and run an incremental job to resolve the issue.

#GC-ChatFileUnsupportedType

Issue:

The file failed in the migration with the following error:

• GC-ChatFileUnsupportedType

Details:

The file type is not supported in the migration.