# How Go shadowing and bad choices caused our first data loss bug in years

DevFeed: [How Go shadowing and bad choices caused our first data loss bug in years](<https://devfeed.tech/articles/how-go-shadowing-and-bad-choices-caused-our-first-data-loss-bug-in-years-35843.md>)

Original publisher: [Read original article](<https://temporal.io/blog/go-shadowing-bad-choices>)

Author: Ryland Goldstein

Published: 2021-03-03T04:00:00Z

Content type: opinion

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [bug](<https://devfeed.tech/topics/bug.md>), [data](<https://devfeed.tech/topics/data.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [reliability](<https://devfeed.tech/topics/reliability.md>), [consistency](<https://devfeed.tech/topics/consistency.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [bug](<https://devfeed.tech/tags/bug.md>), [data](<https://devfeed.tech/tags/data.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [go](<https://devfeed.tech/tags/go.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [shadowing](<https://devfeed.tech/tags/shadowing.md>)

## AI overview

A Temporal retrospective describes the company's first data-loss bug in years. The article attributes the incident to Go shadowing and other bad choices, after initially investigating corrupted workflows and suspected persistence-cluster memory issues.

## Source excerpt

I'm Ryland from Temporal - an MIT OSS platform for building highly reliable distributed applications. We pride ourselves on the reliability and consistency Temporal provides to our users mission critical applications.