
Not sure if this has been posted before because I’ve talked about it with @Jade Thurnham and @Peace Olaniran , but I couldn’t find a thread.
All of a sudden, the user will be tagging, and their PDF goes POOF. Then it comes back after refreshing the page.
I don’t think this happened a few months back, so may be tied to a recent update, like the bibliomining tool, etc?

Yikes, that must mean we have a bug! What are you doing when it disappears?

I am swearing! haha just kidding. I am tagging. Typically when I am using the highlight feature to create a tag.
Jade, and Peace, do you remember when it happened to you?

It happened on this article - https://nested-knowledge.com/gather/tagging_inspector/1930

Which author/year?

Turk, 2007

Interesting, I just tried a couple tags (on Chrome) on that publication without issue :/ Is it happening consistently for you on Turk 2007? Do the same actions trigger it every time?

I am on Chrome too, no it’s only happened once today. But was happening to Jade and Peace a while back, multiple times.

Right, I remember working with Jade on this, and I believed we had resolved that issue (maybe no longer the case?).
Anyways, neither here nor there. I totally believe this is happening! It’s just about impossible for us to debug if the problem if it doesn’t consistently reproduce via somewhat predictable steps. So I’m grasping for a reproducible example we can work on.
If it does happen again, could I have you:
This may indicate to us what’s happening with an error message!

Sounds good Karl, if it comes up again, I will take these steps.

Thank you - I appreciate you bringing this up, sporadic bugs are the worst!


This is still happening for me too! Karl– these are the screenshots I sent you when it was consistently happening to me for reference. I’ll also share screenshots here when it happens again.

Thanks Jade - Kristen, if you could still share what you find, it would be so helpful in validating the error condition!

It happened again and I gathered an error message for ya!

Bummer, but also yay! It’s the same error, which is heartening!

We may have included a fix in 1.37.0, although it’s a bit of a stab in the dark. Please let us know if this continues occurring!