在多个 类 中删除了别名
Aliases removed across multiple classes
我们通过谷歌教室 api 为多个学区创建 类。我们注意到，在 2017 年 12 月 18 日，我们有多个 类 删除了他们的别名（我们最终创建了重复的 类，因为我们将这个别名用作我们的唯一 ID）。我们使用此处定义的域范围别名 https://developers.google.com/classroom/reference/rest/v1/courses.aliases
有什么想法吗？当我们找到更多信息时，我会及时更新。
Google 最终找到了根本原因。这是一个 google 问题。
注意：我确实从 google 中删除了一些消息，但没有任何上下文相关，只是一些与我们公司相关的问题的具体内容。
Hello *****,
I hope this message finds you well. This is a follow up message
concerning your case with Google Cloud Support.
I would like to inform you that we just received an update from our
Engineering Team regarding the bug that was affecting the Classroom
Aliases. According to the update received, our Engineering Team was
able to identify the root cause of the issue and the issue is now
fully resolved. This means that the aliases will no longer clear when
making update to the courses via API. I possible, we would like to
know if you are still seeing aliases that are deleted or seemingly
disappearing?
According to the information and due to the nature of this bug, our
Engineering Team will not be able to restore the previously deleted
aliases but they are working on creating an alternative solution in
case anyone else encounters this issue in the future. This means that
they will have a way to recover aliases in the future in case they are
deleted by a bug or issue in our end. Please rest assured that this
API issue should not occur again but if it does, we will have a way to
get those aliases restored.
I suggest that you recreate the aliases, test to see if there is any
other issues and let me know if you need any additional help or if you
have any questions regarding the above response. Again, we really
appreciate your patience and continued support while we work to
identify the root cause of this issue.
The best way to reach or API Team is by opening a support case and
wait for us to reply back via email or wait for a call back. We will
normally sent an email requesting the best time and phone number to
contact you back. You can also reply to any of our cases during a
period of 30 days and your will be be reopened and I will be able to
contact you back as soon as possible.
Sincerely,
Google Cloud Support
我们通过谷歌教室 api 为多个学区创建 类。我们注意到，在 2017 年 12 月 18 日，我们有多个 类 删除了他们的别名（我们最终创建了重复的 类，因为我们将这个别名用作我们的唯一 ID）。我们使用此处定义的域范围别名 https://developers.google.com/classroom/reference/rest/v1/courses.aliases
有什么想法吗？当我们找到更多信息时，我会及时更新。
Google 最终找到了根本原因。这是一个 google 问题。
注意：我确实从 google 中删除了一些消息，但没有任何上下文相关，只是一些与我们公司相关的问题的具体内容。
Hello *****,
I hope this message finds you well. This is a follow up message concerning your case with Google Cloud Support.
I would like to inform you that we just received an update from our Engineering Team regarding the bug that was affecting the Classroom Aliases. According to the update received, our Engineering Team was able to identify the root cause of the issue and the issue is now fully resolved. This means that the aliases will no longer clear when making update to the courses via API. I possible, we would like to know if you are still seeing aliases that are deleted or seemingly disappearing?
According to the information and due to the nature of this bug, our Engineering Team will not be able to restore the previously deleted aliases but they are working on creating an alternative solution in case anyone else encounters this issue in the future. This means that they will have a way to recover aliases in the future in case they are deleted by a bug or issue in our end. Please rest assured that this API issue should not occur again but if it does, we will have a way to get those aliases restored.
I suggest that you recreate the aliases, test to see if there is any other issues and let me know if you need any additional help or if you have any questions regarding the above response. Again, we really appreciate your patience and continued support while we work to identify the root cause of this issue.
The best way to reach or API Team is by opening a support case and wait for us to reply back via email or wait for a call back. We will normally sent an email requesting the best time and phone number to contact you back. You can also reply to any of our cases during a period of 30 days and your will be be reopened and I will be able to contact you back as soon as possible.
Sincerely,
Google Cloud Support