Observation showing two active IDs from the same user

This observation is showing two simultaneous IDs by user @spacedog, one as Aves and a second as Mimus polyglottos. I would have expected that adding the second ID should automatically cause the first to be withdrawn.

The Birds ID shows as withdrawn when I look at this observation. I see they were added pretty recently. Maybe it was just slow to update?

Thanks. That’s also showing as withdrawn for me. I’m guessing it was some glitch with update processes or indexing. I agree that these IDs were recent, but I’d expect the “ID Withdrawn” tag to be added by the process that adds the replacement ID, not several hours later.

1 Like

I’m seeing the same behaviour on this ob - https://www.inaturalist.org/observations/37875945 - IDs added a day ago…


I’ve seen this happen a number of times recently, but it’s always been fixable by forcing the observation to re-index (e.g. by checking and unchecking a DQA).


I just noticed it here: https://www.inaturalist.org/observations/38213198 and here: https://www.inaturalist.org/observations/38381708.

Thanks @brennafarrell. I looked at your first observation and it was still showing 2 concurrent active IDs from the same user. Then I used @jwidness’s suggestion to toggle a DQA flag and it did indeed change the earlier of the two IDs to “ID Withdrawn”.

On the website, with Chrome: https://www.inaturalist.org/observations/40771420

In the Identify popup, I accidentally double-clicked on Agree. The result is two of the same identification attributed to me at the same time, and neither of them automatically withdrawn.


This is a known bug. It is possible to accidentally create 2 by clicking/tapping too quickly on something. it should not be taken as malicious behaviour by the user because as you saw yourself, it can happen by accident.

It should be safe to delete or withdraw one


Platform: Website

Browser: Chrome

URLs: https://www.inaturalist.org/observations/39049006


Description of problem:
It seems that I was able to post two Common Raven IDs on this observation and the system recognizes it as two. Typically isn’t one of the IDs supposed to marked as withdrawn?

Yes, for sure, though it has been suggested that the system should just automatically block a second, duplicate ID like this.

Do you happen to recall the sequence of steps that resulted in these two IDs? Were they both added via the website, or could one have come from a mobile app?

It will be interesting to see if this “fixes itself” if/when someone else adds another ID. I would suggest not touching the obs until the developers can take a look, but that’s probably impossible to prevent at this point.

I don’t have the mobile app, so that wasn’t how I could have added two IDs. I think the two IDs might have come from the fact that I posted the comment in the Obs just before I clicked agree. When the loading symbol disappeared, only the comment was left, and it showed me as having not made an ID. So, I clicked agree again and either when the loading sign disappeared or when I exited out and back in of the observation did it show me as making two IDs.

1 Like

I agreed with the ID, and the first one looks withdrawn to me.

1 Like

Yep, so just for the record, prior to your new ID being added, I did follow the link to the observation several times, and it was still in the state shown in the screen shot above.

This seems to be related to: https://forum.inaturalist.org/t/observation-showing-two-active-ids-from-the-same-user/9681.


Well, whatever it was, it seems to be fixed by alexis_orion’s ID.

1 Like

I wonder if it counted as two IDs for the CID algorithm…

What’s the CID algorithm?

It looks like it did. The screenshot shows 3 IDs for the community id.

CID = Community id.

Yes, like many similar issues that get reported, this was probably a case of background indexing of the first ID not having completed before the second ID got added. Further changes to the observation force it to be re-indexed and generally end up fixing the issue.

I looked at the time, and it definitely was counting as two, until the new ID forced the re-index. You can see that in the screenshot too.