64 replies · 765 views · thread synced · 6 days ago
· View on torn.com
About this thread
Posts archived:65 / 65 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
Archived posts
65
Discussion span
→
Authority score
63 / 100
Historical score
46 / 100
Story score
55 / 100
Engagement score
76 / 100
People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.
Most-liked replies
IceBlueFire[776]Officer
· 5 likes · It seems to be very random, as in, there's no specific one call that triggers the error to respond and it's very intermittent. However, i do believe it might be a collision issue of some kind. I believe it's more …
jjinn[2042332]
· 3 likes · Here is the error I've gotten every time since the Torn update was released: Your file was not found It may have been moved or deleted. ERR_FILE_NOT_FOUND
Mauk[1494436]
· 2 likes · It's still happening to DoctorN users, including myself. I've gotten multiple reports the past 2 days.
I'm not exactly sure what is wrong here, but a lot of people are experiencing DoctorN throwing an 'Invalid Key' error. This is not a DoctorN issue, though - as the only way that could happen is if that error comes from Torn's API server. I'm just asking if this could be checked, to ensure nothing is wrong with the API.
I have reset my key as well and it's still happening.
It does when I try it, but for some reason, the extension just keeps throwing invalid key (only possible if that error is received). Which is why I raised this bug report - for this to be checked server side for anything wrong.
It seems to be very random, as in, there's no specific one call that triggers the error to respond and it's very intermittent. However, i do believe it might be a collision issue of some kind. I believe it's more likely to occur when you make two requests at the same time. I'm not sure if this is a thing, but it's about the only thing that i can see makes sense here.
I've noticed this happening a number of times both from DoctorN and through my site Torn Stats where it randomly responds with an Invalid Key error and wipes out the key (as a safeguard in the systems).'
I'm not sure if i recall this correctly, but i believe you guys were working on transaction locking as one of the backend updates. This is why i'm thinking it might be related to that, however i don't know for sure.
During last few days we experienced some issues with overall error handling that should be fixed now I believe. Is this still occur or it was like that only some time ago?
I can't replicate, unfortunately, I am ending with 'too many requests' in all my automated tests. 'Wrong key' error can occur only if we somewhat were unable to read the key from DB, for example because of wrong format. There are no locking or transaction on this, as this is just a read only.
Otherwise, i'm just tossing ideas out. I don't know how else to replicate it. But you can see here all the times that it's returned with a invalid key, even though i haven't changed my key at all (just re-entered it)
I was being logged out while just sitting there. There is probably still requests being made without me initiating it, but all my log outs of DocN were when I was idle.
![[image: image.prntscr.com]](https://image.prntscr.com/image/6mR_BGSZSA_ouRZN2SsHSA.png){kind=link}