I've been having this problem on some 1/5 of my reasonably substantial edits. I have not yet had it on a talk page reply using the reply tool. I've also been getting "session failure" while using CU, though much less frequently than 1/5 of the time. I basically never used to have this problem with CU at all (only when I really did actually leave a window open for hours and then press a button) but I think I've had it happen upwards of a dozen times in the past two or three days.

In individual log/edit rows, it would be helpful if the ja3n/ja4h data was on a new line. This would make it easier to compare fingerprints (because the same parts of the fingerprint would be in roughly the same horizontal location instead of being moved around based on the CH data) and make it easier to skim-read the CH line.

These have pretty high value for sock-hunters, especially non-admin/non-CU sock-hunters. I would miss them a lot. SPI clerks would miss them much more.

one giant YES PLEASE from en-wiki SPI over here

I agree that this is a problem that should be higher priority. Honestly, if a quick fix is desired, we could even disable the title search outright and only allow ISBN, etc. I have literally never had the correct item show up when I have used title search. Frankly, I had completely forgotten you even could title search with the citations tool.

Update: it failed for me on every single one of the individual discussion pages here: https://en.wikipedia.org/wiki/Wikipedia:Administrator_elections/July_2025/Discussion_phase . Refreshing (up to three times) never succeeded. Safemode worked every time. So that's a total of six failures that appear reproduceable. Will mess around with my common.js and see if I can find what's causing it.

This happens to me all the time. I can sometimes fix it by refreshing the page, sometimes not. Sometimes it takes several refreshes. I thought it was the markblocked gadget that was screwing with things, but turning that off only solved the problem for a little while. How it solved the problem at all for any period of time is a total mystery to me. Nothing illuminating in the console. I experience the same problem across multiple browsers. I feel like it happens more often on longer pages and when linked via notifications, but that might be just in my head. I've tried safe mode to fix it a handful of times and it's worked, but since refreshing the page can also fix the problem and the problem can't be reliably reproduced, I'm not sure whether I can conclude anything from that.

Help:Getting started is another possibility, but I don't think that's on all the wikipedias either.

Hi, I'm the aforementioned "another user", just here to reaffirm that I think it's better without the "unfortunately" at all (don't apologize for your bot! just tell people how to fix it if it screws up), and also to point out that "automated system which uses" should be "automated system that uses".