Yammer

【トラブルシューティング】投稿やコメント、メッセージが期待通りに表示されずフィードが読み込まれない場合がある SI(サービス インシデント)が発生!【YA314035】【PIR】【復旧済み】

トラブルシューティング
0 0
Read Time:22 Minute, 40 Second
Yammer
Yammer

Microsoft が提供する Microsoft 365 のサービス正常性(YA314035)にて、Yammer への投稿やコメント、メッセージが期待通りに表示されずフィードが読み込まれない場合がある SI(サービス インシデント)が発生していることを発表しています。

現在は影響していたシナリオへの対処が完了しており、広範なテストの結果、この問題が完全に解決していることを確認しているとのことです。

  • ・新規投稿の閲覧が行えない
  • Yammer のフィードの読み込みが行えない
  • ・メッセージが表示されず、”Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.” というエラー メッセージが表示される
  • ・SI(サービス インシデント)発生中に送信されるはずの通知が送信されない

なお、この問題の解決後もごく一部のユーザーにて以下の影響が残っている可能性もあります。

  • ・SI(サービス インシデント)発生により、固定されていた一部の投稿の固定が解除解除されている可能性があります。
  • ・回答済みの質問が未回答のフィードに表示されることがあります。
  • ※ “ベスト アンサー” はハイライトされたままになります。
  • ・SI(サービス インシデント)発生中にコミュニティーからコミュニティーへスレッドを移動すると両方のコミュニティーでスレッドが重複して表示されることがあります。

ただし、上記に記載されているシナリオにおいては引き続き影響が残っている可能性があるため、影響緩和に関する最新のスケジュールは今週末に発表される予定とのことです。

この問題は Azure データベース パーティションの一部で可用性の状態が安定しないことにより、最適なレベル以下で動作したことから本事象に影響し発生していたとのことです。

現在は、可用性の問題とその後のサービスへの影響への根本的な原因を特定するために追加で調査を行っており、近日中に発行予定の事後報告書にて発表されるとのことです。

なお、5 営業日以内に PIR(Post – Incident Report)が公開されます。

※ 本事象は該当するインフラストラクチャーを経由しているすべてのユーザーにて影響を受けている可能性があるとのことです。

また、最初の問題の解決後も一部のユーザーには影響が残っている可能性があります。




created by Rinker
¥11,603 (2022/05/22 08:26:43時点 Amazon調べ-詳細)

PineApple では記事内リンクからアフィリエイト報酬を得ることで当サイトの運営および維持を行っておりますため、ご協力いただけますと幸いです。

Users’ Yammer posts, comments, and messages aren’t being displayed as expected – YA314035

サービス:Yammer

状態:Service restored

ユーザーへの影響:Users’ Yammer posts, comments, and messages aren’t being displayed as expected.

Microsoft 365 のサービス正常性(YA314035)にて、Yammer への投稿やコメント、メッセージが期待通りに表示されずフィードが読み込まれない場合がある SI(サービス インシデント)が発生していることを発表しています。

現在は影響していたシナリオへの対処が完了しており、広範なテストの結果、この問題が完全に解決していることを確認しているとのことです。

  • ・新規投稿の閲覧が行えない
  • Yammer のフィードの読み込みが行えない
  • ・メッセージが表示されず、”Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.” というエラー メッセージが表示される
  • ・SI(サービス インシデント)発生中に送信されるはずの通知が送信されない

なお、この問題の解決後もごく一部のユーザーにて以下の影響が残っている可能性もあります。

  • ・SI(サービス インシデント)発生により、固定されていた一部の投稿の固定が解除解除されている可能性があります。
  • ・回答済みの質問が未回答のフィードに表示されることがあります。
  • ※ “ベスト アンサー” はハイライトされたままになります。
  • ・SI(サービス インシデント)発生中にコミュニティーからコミュニティーへスレッドを移動すると両方のコミュニティーでスレッドが重複して表示されることがあります。

ただし、上記に記載されているシナリオにおいては引き続き影響が残っている可能性があるため、影響緩和に関する最新のスケジュールは今週末に発表される予定とのことです。

この問題は Azure データベース パーティションの一部で可用性の状態が安定しないことにより、最適なレベル以下で動作したことから本事象に影響し発生していたとのことです。

現在は、可用性の問題とその後のサービスへの影響への根本的な原因を特定するために追加で調査を行っており、近日中に発行予定の事後報告書にて発表されるとのことです。

なお、5 営業日以内に PIR(Post – Incident Report)が公開されます。

※ 本事象は該当するインフラストラクチャーを経由しているすべてのユーザーにて影響を受けている可能性があるとのことです。

また、最初の問題の解決後も一部のユーザーには影響が残っている可能性があります。






Post Incident Repot(PIR)

Incident Information

Important Note
  • This is a preliminary Post Incident Report (PIR) that is being delivered to provide early insight into details of the issue.
  • The information in this PIR is preliminary and subject to change.
  • A final PIR will be provided within five (5) business days from full event resolution and will supersede this document upon publication.
Incident ID
YA314035
Incident Title
Users’ Yammer posts, comments, and messages weren’t displayed as expected.
Service(s) Impacted
Yammer

User Impact

Newly created Yammer posts, comments, and messages weren’t delivered to other users as expected.

  • ・Additionally :
  • – Messages were not displaying as expected and users would have noticed this error message :
  • “Your message was successfully posted but isn’t displaying right now. You could refresh in a few minutes to see it.”
  • – Users had issues loading Yammer feeds in approximately 3% of cases.
  • – Notifications that should have been sent during the affected outage were not sent.

After the core issue was resolved, a very small number of users may have still experienced the following residual impact scenarios :

  • – Some posts that were pinned during the impact may have become unpinned.
  • – Answered questions may have appeared in the unanswered feed; however, the “best answer” would have remained highlighted.
  • – Moving thread from community to community during the outage window would have caused the thread to appear in both communities.

Scope of Impact

Any user routed through the affected infrastructure in the North America region may have been affected.

Once the initial service issue was resolved, a small subset of users may have continued to experience some residual impact as described above.

Customers served through infrastructure hosted in the EMEA region were unaffected.

Incident Start Date and Time

Thursday, January 13, 2022, at 3:56 AM UTC

Incident End Date and Time

Friday, January 14, 2022, at 9:26 AM UTC

Root Cause

A portion of Yammer’s database shards entered a degraded state.

As such, the remaining shards were unable to process new requests, thereby preventing message delivery to Yammer feeds and inboxes.

Actions Taken (All times UTC)

Thursday, January 13
  • ・4:06 AM – We received reports from telemetry that indicated message delivery delays within Yammer.
  • We started to analyze analytics to understand the cause and develop a fix.
  • ・4:22 AM – We determined that customers would see the message “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • However, users would have been able to read their feeds and create messages.
  • We continued our efforts to analyze logs.
  • ・5:01 AM – We discovered that the affected functionality is dependent on an internal database system which wasn’t responding to the service as expected.
  • ・6:15 AM – We investigated analytics from the service and the diagnostics from the database system to identify the root cause.
  • ・10:33 AM – We determined that some shards were unavailable, indicating that we would need to start a database restore from a snapshot backup taken several hours prior to the incident.
  • ・11:18 AM – We initiated the recovery of the affected shards from a previous backup.
  • We estimated that the database restore would take between 5-10 hours.
  • ・11:45 AM – While waiting for database restore to complete, users continued to post new messages, but messages sent after the timestamp of the restore would need to be re-applied.
  • We began analyzing and planning for the reingestion process of messages delivered after the time of database restore snapshot.
  • ・5:05 PM – The database restore completed, and we began the process of re-applying message actions and deletes that were affected during the impact window.
  • We designed, coded, and deployed service changes to replay events currently in this state.
  • ・10:19 PM – There were multiple event streams for various Yammer message types and user actions, and due to the complex nature of reingestion of these activities, it took an extended amount of time to develop, test, and verify the results.
  • We took additional precautions during this time, to ensure that the overall system would arrive at a consistent state.
Friday, January 14
  • ・1:35 AM – We made additional configuration changes to the database prior to restoration.
  • After the configuration changes were applied and the new database was brought online, feed loading errors as described in the user impact section recovered.
  • While affected feeds started loading correctly, the latest messages weren’t appearing yet.
  • ・3:02 AM – We began re-applying impacted messages and actions in a specific order, to ensure overall system consistency.
  • While this re-delivery process was underway, users would continue to see message delays.
  • ・9:26 AM The backlog of delayed message delivery and delete events was fully processed, and message events caught up to “real time”.
  • As such, Yammer’s core features of message posting, message delivery, and feed loading were restored at this time.
  • ・9:40 AM Based on telemetry and customer reports, we investigated additional notification related delays and confirmed a large queue of delayed notifications had built up.
  • Because notifications are time-sensitive, we dropped the backlog of notifications in the queue, thus restoring current “real time” notifications to normal operation.
  • ・7:15 PM – We validated service health across all features. During this process we identified additional impact scenarios for approximately three percent of cases, which were listed in the Service Health Dashboard (SHD) notification.
  • We began our efforts to fix the residual issues.
  • ・10:00 PM – We developed an action plan to address the residual impact.
  • Which included but were not limited to configuration changes and checks to existing functionalities
Thursday, January 20
  • ・1:13 AM – We validated that all residual impact referenced in the user impact statement above were fully resolved.

Next Steps

Findings
Action
Completion Date
  • A portion of Yammer’s database shards were in a degraded state.
  • As such, the remaining shards were unable to process new requests, thereby preventing message delivery to Yammer feeds and inboxes.
We’re performing an additional investigation to determine the underlying cause of the availability issues and subsequent service impact.
February 2022
We’re implementing additional alerting mechanisms that will allow us to identify and prevent issues of a similar nature from occurring.
In Progress

January 20, 2022 10:22 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages weren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages weren’t being displayed as expected.
  • ・Final status : We’ve completed addressing the lingering impact scenarios outlined in the “More Info” section and have confirmed after extensive testing that the issue is fully resolved.
  • ・More info :
  • – Users were unable to see new posts being created.
  • – Users had issues loading Yammer feeds.
  • – Messages were not displaying as expected and would have noticed this error message :
  • “Your message was successfully posted but isn’t displaying right now. You could refresh in a few minutes to see it.”
  • – Notifications that should have been sent during the affected outage were not sent.
  • ・After this issue was resolved, a very small number of users may have still experienced the following residual impact scenarios :
  • – Some posts that were pinned during the impact may have become unpinned.
  • – Answered questions may have appeared in the unanswered feed; however, the “best answer” would have still remained highlighted.
  • – Moving thread from community to community during the outage window would have caused the thread to be duplicated in both communities.
  • ・Scope of impact : Any user routed through the affected infrastructure may have been affected.
  • Once the initial service issue was resolved, a small subset of users may have continued to experience some residual impact.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・End time : Saturday, January 15, 2022, 6:26 AM (1/14/2022, 9:26 PM UTC)
  • ・Preliminary root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • Next steps :
  • – We’re performing an additional investigation to determine the underlying cause of the availability issues and subsequent service impact.
  • – Additional action items will be provided in the forthcoming post-incident report.
  • We’ll publish a post-incident report within five business days.

January 18, 2022 3:24 PM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Primary Yammer functionality is restored. These scenarios are no longer affected :
  • – Users were unable to see new posts being created
  • – Users had issues loading Yammer feeds
  • – Messages were not displaying as expected and would have noticed this error message :
  • “Your message was successfully posted but isn’t displaying right now.
  • You can refresh in a few minutes to see it.”
  • – Notifications that should have been sent during the affected outage were not sent
  • – Reports of data export was not working from Shell.
  • ・Users may still experience the following residual impact scenarios :
  • – Some posts that were pinned during the impact may have become unpinned.
  • – Answered questions may appear in the unanswered feed; however, the “best answer” will still remain highlighted.
  • – Moving thread from community to community during outage window would cause the thread to be duplicate in both communities.
  • ・Current status : We’ve confirmed that primary Yammer functionality including inability to see new posts, failure loading Yammer, and messages displaying incorrectly has been fully resolved.
  • However, some users may still be experiencing some residual impact to the scenarios listed in the “More info” section above.
  • We anticipate having an updated timeline for the residual impact mitigation later this week.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Wednesday, January 19, 2022, 11:00 AM (2:00 AM UTC)

January 15, 2022 10:07 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users did not see new posts being created and may have seen issues loading Yammer feeds and messages not displaying as expected.
  • ・Users may have encountered the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Additionally, users may experience these potentially related impact scenarios :
  • – Actions to pin or unpin a post may not have occurred during the outage window.
  • – Some posts that were pinned during the impact may have become unpinned.
  • – Answered questions may appear in the unanswered feed; however, the “best answer” will still remain highlighted.
  • – Moving thread from community to community during outage window would cause the thread to be duplicate in both communities.
  • These scenarios are no longer affected :
  • – Notifications that should have been sent during the affected outage were not sent.
  • – Reports of data export was not working from Shell.
  • ・Current status : Our efforts to restore the backlogged data are progressing as expected.
  • In parallel, we are continuing to address the residual impact scenarios for this event.
  • At this time, the scenarios listed in the “More info” section remain impacted.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Wednesday, January 19, 2022, 10:30 AM (1:30 AM UTC)

January 15, 2022 6:30 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users did not see new posts being created and may have seen issues loading Yammer feeds and messages not displaying as expected.
  • ・Users may have encountered the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • Whilst we process the backlog of events, some users may experience delays in receiving Teams, Outlook, and mobile notifications.
  • ・Additionally, users may experience these potentially related impact scenarios :
  • – Community badges may be inaccurate for communities with pinned posts.
  • – Pinned posts may not display properly.
  • – Some posts that were pinned during the impact may have become unpinned.
  • We are working to restore these pinned items.
  • – Notifications that should have been sent during the affected outage will not be sent.
  • They may show up in the next daily digest email.
  • – Threads that users had muted may have been unmuted.
  • – Users may see duplicate posts in scenarios where users reposted multiple times when they were unable to see the initial post.
  • ・Current status : The backlog of affected data is being processed without interruption and core Yammer functionality continues to remain stable.
  • We’re monitoring the identified residual impact scenarios and we’ll provide updated information as it becomes available.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Saturday, January 15, 2022, 10:30 AM (1:30 AM UTC)

January 15, 2022 4:29 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users did not see new posts being created and may have seen issues loading Yammer feeds and messages not displaying as expected.
  • ・Users may have encountered the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • Whilst we process the backlog of events, some users may experience delays in receiving Teams, Outlook, and mobile notifications.
  • ・Additionally, users may experience these potentially related impact scenarios
  • – Community badges may be inaccurate for communities with pinned posts.
  • – Pinned posts may not display properly.
  • – Some posts that were pinned during the impact may have become unpinned.
  • We are working to restore these pinned items.
  • – Notifications that should have been sent during the affected outage will not be sent.
  • They may show up in the next daily digest email.
  • – Threads that users had muted may have been unmuted.
  • – Users may see duplicate posts in scenarios where users reposted multiple times when they were unable to see the initial post.
  • ・Current status : We’ve confirmed that core Yammer functionality is restored and are continuing to process the backlog of events that were affected, during this period users may continue to experience delays in receiving Teams, Outlook, and mobile notifications.
  • While this process continues, we’re investigating reports of potentially related impact scenarios listed in the More Info section, and we’ll provide an ETA for resolution as soon as one becomes available.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Saturday, January 15, 2022, 6:30 AM (1/14/2022, 9:30 PM UTC)

January 15, 2022 2:35 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may have seen that Yammer live event posts, comments, and messages weren’t displaying as expected, and feeds may not have loaded.
  • ・Users may have encountered the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Current status : We’ve resolved the issue that was slowing our infrastructure re-sync and have restored core Yammer functionality.
  • Whilst we process the backlog of events, some users may experience delays in receiving Teams, Outlook, and mobile notifications.
  • Some posts that were pinned during the impact period may have become unpinned and we are working to restore these pinned items.
  • Additionally, there may be occurrences of post duplication in scenarios where users reposted multiple times when they were unable to see the initial post.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Saturday, January 15, 2022, 4:30 AM (1/14/2022, 7:30 PM UTC)

January 14, 2022 11:56 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may also see that Yammer live event posts, comments, and messages aren’t displaying as expected, and feeds may not load.
  • ・Users may encounter the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Current status : We’re working to resolve an unexpected issue that’s slowing our infrastructure re-sync and reconfiguration.
  • In parallel, we’re preparing the service to backfill the affected user content, which we’ll initiate once our infrastructure work completes.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Saturday, January 15, 2022, 4:30 AM (1/14/2022, 7:30 PM UTC)

January 14, 2022 9:53 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may also see that Yammer live event posts, comments, and messages aren’t displaying as expected, and feeds may not load.
  • ・Users may encounter the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Current status : We’re manually re-syncing and reconfiguring our infrastructure to ensure that the data is reprocessed by the service as efficiently as possible.
  • Once we’ve completed more of this work, we’ll be able to provide an estimated mitigation timeline.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Friday, January 14, 2022, 12:00 PM (3:00 AM UTC)

January 14, 2022 6:59 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may also see that Yammer live event posts, comments, and messages aren’t displaying as expected, and feeds may not load.
  • Users may encounter the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Current status : We’re assessing the most efficacious way to complete the reconfiguration of the new infrastructure and address the backlog of data, which we anticipate may take some time to process.
  • We’re working on identifying a mitigation timeline to share in our next communication.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were in an inconsistent state of availability, causing the remaining partitions to operate at sub-optimal levels and resulting in impact.
  • ・Next update by : Friday, January 14, 2022, 10:00 AM (1:00 AM UTC)

January 14, 2022 3:58 AM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may also see that Yammer live event posts, comments, and messages aren’t displaying as expected, and feeds may not load.
  • ・Users may encounter the following error : “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Current status : We’ve confirmed that the restoration of the Azure database partitions has completed.
  • We’re now verifying the restored data and reconfiguring the new infrastructure to ensure that these actions provide relief.
  • ・Scope of impact : Any user routed through the affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Root cause : A portion of Azure database partitions were unavailable and causing the remaining partitions to operate at sub-optimal levels, resulting in impact.
  • ・Next update by : Friday, January 14, 2022, 7:00 AM (1/13/2022, 10:00 PM UTC)

January 13, 2022 11:04 PM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may encounter the following error: “Your message was successfully posted but isn’t displaying right now. You can refresh in a few minutes to see it.”
  • ・Current status : We’ve initiated the restoration of the impacting Azure database partitions, which we estimate will take up to 7 hours to complete.
  • ・Scope of impact : Any user routed through affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Next update by : Friday, January 14, 2022, 4:00 AM (1/13/2022, 7:00 PM UTC)

January 13, 2022 8:59 PM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may encounter the following error: “Your message was successfully posted but isn’t displaying right now.
  • You can refresh in a few minutes to see it.”
  • ・Current status : We’ve identified that some of our Azure database partitions are unavailable. We’re preparing to restore them via our backup, to remediate impact.
  • Once the partitions are restored, we’ll confirm that message deliveries have started again.
  • ・Scope of impact : Any user routed through affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Next update by : Friday, January 14, 2022, 12:00 AM (1/13/2022, 3:00 PM UTC)

January 13, 2022 6:58 PM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may encounter the following error: “Your message was successfully posted but isn’t displaying right now.
  • You can refresh in a few minutes to see it.”
  • ・Current status : We believe impact is being caused by an issue with a specific part of our Azure database service.
  • We’re analyzing Azure logs to help us validate this.
  • ・Scope of impact : Any user routed through affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Next update by : Thursday, January 13, 2022, 9:00 PM (12:00 PM UTC)

January 13, 2022 4:11 PM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may encounter the following error : “Your message was successfully posted but isn’t displaying right now.
  • You can refresh in a few minutes to see it.”
  • ・Current status : We’re investigating our affected infrastructure to understand why this impact is occurring within our service and determine the most expedient approach to resolution.
  • ・Scope of impact : Any user routed through affected infrastructure may be affected.
  • ・Start time : Thursday, January 13, 2022, 12:56 PM (3:56 AM UTC)
  • ・Next update by : Thursday, January 13, 2022, 7:00 PM (10:00 AM UTC)

January 13, 2022 3:58 PM – Service restored

  • ・Title : Users’ Yammer posts, comments, and messages aren’t being displayed as expected
  • ・User Impact : Users’ Yammer posts, comments, and messages aren’t being displayed as expected.
  • ・More info : Users may encounter the following error : “Your message was successfully posted but isn’t displaying right now.
  • You can refresh in a few minutes to see it.”
  • ・Current status : We’re investigating a potential issue and checking for impact to your organization.
  • We’ll provide an update within 30 minutes.

Microsoft Public Affiliate Program (JP)(マイクロソフトアフィリエイトプログラム)

Yammer 関連記事一覧

Yammer 関連記事一覧

Yammer のメッセージ センター関連情報一覧

Yammer のメッセージ センター関連記事一覧

デル株式会社

Yammer サービス正常性 関連記事一覧

Yammer サービス正常性 関連記事一覧

関連リンク




Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

コメントを残す

メールアドレスが公開されることはありません。 * が付いている欄は必須項目です

このサイトはスパムを低減するために Akismet を使っています。コメントデータの処理方法の詳細はこちらをご覧ください