Tag randomly change after requeuing

[Archross]

The issue occurred in my Image Bounding Box dataset which has 15 tags. After I requeued the tagged images while evaluating the tagging, one of the tags in the requeued somehow changed to another tag completely. For example, the image previously had ten car bounding boxes but after the re-queued all of those bounding box's tags were changed to tree instead.

This issue happens randomly and I have no idea what's the cause. I am pretty confident that it isn't a human error because this happened to two different annotators and it is the same tag that was changed.

Does anyone also have this problem? How should I try to investigate it?

[GokulNC]

Technically, there will be a status flag associated with each data corresponding to a HIT that's stored in the DB.
When you requeue, the backend just changes the status of the flag from DONE to REQUEUED if I remember correctly.
That is, basically, your HIT data will not be parsed or modified when you requeue.

So, I think there should be some other reason or probably in the requeue code flow that's causing it.
What you could try it to replicate the issue by trying to create a new task with a very few images (1-5) and do your thing until you're able to reproduce the error.

That should provide some hint maybe, about the exact user behavior that causes the issue.