# The ID I made on my observation updated itself

**URL:** <https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233>\
**Category:** Bug Reports\
**Created:** [July 22, 2019, 7:07pm UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233 "2019-07-22T19:07:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cedric\_lee](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.inaturalist.org/cedric_lee/32/504_2.png) [@cedric\_lee](https://forum.inaturalist.org/u/cedric_lee)\
**Post date:** [July 22, 2019, 7:07pm UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233/1 "2019-07-22T19:07:06Z")

</div>

Is there a bug where your identification changes automatically (excluding those caused by taxa changes)?  
Below are two recent instances where my identifications changed without my approval. I’ve only noticed these since I got updates from my dashboard regarding comments/IDs made on the observations.

[https://www.inaturalist.org/observations/10029166](https://www.inaturalist.org/observations/10029166)  
 ![2019-07-20_1834](https://us1.discourse-cdn.com/flex016/uploads/inaturalist/original/2X/5/513f98867fcdc55c47adc9b3770a3b7e60cf868c.jpeg)

[https://www.inaturalist.org/observations/1693975](https://www.inaturalist.org/observations/1693975)  
 ![2019-07-22_1200](https://us1.discourse-cdn.com/flex016/uploads/inaturalist/original/2X/c/c8a753fef463beae04631b729ee805fd6390a45f.jpeg)

---

<div class="post-metadata">

**Author:** ![tiwane](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.inaturalist.org/tiwane/32/54612_2.png) [@tiwane](https://forum.inaturalist.org/u/tiwane)\
**Post date:** [July 22, 2019, 9:49pm UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233/2 "2019-07-22T21:49:17Z")

</div>

Weird, we’ll look into it. Any other examples?

---

<div class="post-metadata">

**Author:** ![cedric\_lee](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.inaturalist.org/cedric_lee/32/504_2.png) [@cedric\_lee](https://forum.inaturalist.org/u/cedric_lee)\
**Post date:** [July 22, 2019, 10:52pm UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233/3 "2019-07-22T22:52:53Z")

</div>

Not that I’ve found, but I’m keeping an eye out.

---

<div class="post-metadata">

**Author:** ![jdmore](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.inaturalist.org/jdmore/32/1116_2.png) [@jdmore](https://forum.inaturalist.org/u/jdmore)\
**Post date:** [July 23, 2019, 12:33am UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233/4 "2019-07-23T00:33:44Z")

</div>

Without knowing any context, your first example might be attributable to an accidental hit on an “Agree” button (I’ve been known to do this occasionally) while looking at the observation. But the second one wouldn’t fit that explanation. If it were me, I might just be paranoid enough to change my account password. But there would probably be other indications if an account had been compromised…

---

<div class="post-metadata">

**Author:** ![cedric\_lee](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.inaturalist.org/cedric_lee/32/504_2.png) [@cedric\_lee](https://forum.inaturalist.org/u/cedric_lee)\
**Post date:** [July 23, 2019, 12:47am UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233/5 "2019-07-23T00:47:05Z")

</div>

Yeah, I changed my password as a precaution. I thought about accidentally hitting the agree button in hindsight, but I had no reason nor do I recall going back to these observations to change their ID.

---

<div class="post-metadata">

**Author:** ![tiwane](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.inaturalist.org/tiwane/32/54612_2.png) [@tiwane](https://forum.inaturalist.org/u/tiwane)\
**Post date:** [July 23, 2019, 3:41am UTC](https://forum.inaturalist.org/t/the-id-i-made-on-my-observation-updated-itself/5233/6 "2019-07-23T03:41:48Z")

</div>

After a preliminary look into this, we think it’s likely a bug on our end. If any can come up with conditions by which we can reproduce this, that would be helpful. It _might_ affect only those users who aren’t accepting Community ID.
