| Recurring |
one_organization |
(a) The software failure incident related to incorrectly marking posts as spam on Facebook due to a bug in the anti-spam system has happened again within the same organization. Facebook acknowledged that this incident was caused by a software issue, specifically a bug in their anti-spam system [97470]. This incident led to posts on various topics, including coronavirus-related content, being wrongly marked as spam, resulting in widespread complaints from users. The issue arose after Facebook had announced sending home contract workers who perform content review services due to the outbreak, indicating a recurrence of the software failure incident within the organization. |
| Phase (Design/Operation) |
design |
(a) The software failure incident mentioned in the articles can be attributed to the design phase. Facebook acknowledged that the incorrectly marked spam posts, including those related to coronavirus, were due to a bug in their anti-spam system. This bug introduced by the system development led to posts being wrongly flagged as spam, causing widespread complaints from users [97470]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident reported in the article is attributed to a bug in Facebook's anti-spam system, which incorrectly marked posts on various topics, including coronavirus, as spam. Facebook's head of safety mentioned, "This is a bug in an anti-spam system" [97470]. This indicates that the failure originated from within the system itself, specifically from the anti-spam system.
(b) outside_system: The article does not provide information suggesting that the software failure incident was caused by contributing factors originating from outside the system. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident in this case was attributed to a bug in an anti-spam system on Facebook, which incorrectly marked posts on various topics, including coronavirus, as spam. This bug was a non-human action that led to the failure [97470].
(b) Additionally, human actions were involved in the response to the incident. Facebook announced sending home contract workers who review content due to the outbreak, which could have contributed to longer response times and potential mistakes in handling such issues [97470]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident reported in the article is attributed to a bug in an anti-spam system on Facebook, which incorrectly marked posts on various topics, including coronavirus, as spam. This bug led to widespread complaints from users and required the restoration of all incorrectly removed posts [97470].
(b) The software failure incident is specifically mentioned to be caused by a bug in an anti-spam system on Facebook, indicating that the contributing factor for this failure originates in the software itself [97470]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident mentioned in the article is non-malicious. Facebook attributed the issue to a bug in their anti-spam system, which incorrectly marked posts on various topics, including coronavirus, as spam. The company's head of safety stated that it was a software issue and not a deliberate act of malicious intent [97470]. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The software failure incident mentioned in the article was not due to poor decisions but rather a bug in an anti-spam system on Facebook that incorrectly marked posts, including those related to coronavirus, as spam. This bug led to widespread complaints from users and required the restoration of the incorrectly removed posts [97470]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident related to development incompetence is not explicitly mentioned in the provided article.
(b) The software failure incident related to accidental factors is evident in the article. Facebook attributed the issue of posts on topics like coronavirus being wrongly marked as spam to a software bug in their anti-spam system. This indicates that the failure was accidental and not intentional [97470]. |
| Duration |
temporary |
(a) The software failure incident mentioned in the article was temporary. It was caused by a bug in an anti-spam system on Facebook that incorrectly marked posts, including those related to coronavirus, as spam. Facebook acknowledged the issue and restored all the incorrectly removed posts, indicating that it was a specific incident caused by the bug in the system [97470]. |
| Behaviour |
value, other |
(a) crash: The software failure incident reported in the article is not related to a crash where the system loses state and does not perform any of its intended functions. [97470]
(b) omission: The software failure incident is not due to the system omitting to perform its intended functions at an instance(s). It is more related to incorrectly marking posts as spam. [97470]
(c) timing: The software failure incident is not due to the system performing its intended functions correctly but too late or too early. It is more about incorrectly marking posts as spam. [97470]
(d) value: The software failure incident is related to the system performing its intended functions incorrectly by marking posts on topics including coronavirus as spam. This behavior was attributed to a bug in an anti-spam system. [97470]
(e) byzantine: The software failure incident is not related to the system behaving erroneously with inconsistent responses and interactions. It is more about incorrectly marking posts as spam. [97470]
(f) other: The software failure incident behavior is specifically related to a bug in an anti-spam system that led to posts on various topics, including coronavirus, being wrongly marked as spam. This behavior resulted in widespread complaints from users. [97470] |