Skip to content
TORNLIFE More

API randomly returning null logs

Started by Skeletron [318855] on in Bugs & Issues.

9 replies · 246 views · thread synced · 7 days ago · View on torn.com
About this thread

Posts archived: 10 / 10 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
10
Discussion span
→
People posting
6
Likes on archived posts
3
Posts by staff, officers and moderators
4
Authority score
57 / 100
Historical score
39 / 100
Story score
41 / 100
Engagement score
54 / 100

Most-liked replies

  • aurel1 [1046304] Admin · 1 likes ·
    I will ask Sergey to check that - last similar issue was related to the error handling
  • serhiid [2307949] Admin · 1 likes ·
    Hello This issue was fixed. Changes will be applied soon. It was related to an unhandled backend error. Now instead broken response will appear appropriate error. Thanks!

Mentioned in this thread

Redxjak [2255595] ×1

Skeletron [318855] · #1
I'm randomly getting {"log":null} from the API, usually happening after long response times.

If I wait a bit then retry with the same parameters, it correctly returns the entries.
Skeletron [318855] · #4
It happened while pulling the Travel log category.

Redxjak's Profile | TORN had the same issue with Crimes category yesterday.

Just tested and had it happen with the "Attack mug" log too: https://api.torn.com/user/?selections=log&log=8155&from=0&to=1666999749&comment=tornreport&key=[redacted]

Mentions: Redxjak [2255595]

MrRightSA [2652679] · #6
For me,

It's happening with stat calls on Torn Tools (xanax use, cans etc.)
It happens with faction spies through torn stats
It happens with a call to check a users job/stars

Everything basically. It will fail as it takes too long then you refresh and it has worked.
Skeletron [318855] · #7
Some more information in case it's helpful:

I'm also getting {"log":null} from some requests completing under 500ms, not just after long response times. Sometimes repeating the request right away gives the expected response, other times it's also {"log":null}.
serhiid [2307949] Admin Staff · #9
Hello
This issue was fixed. Changes will be applied soon.
It was related to an unhandled backend error. Now instead broken response will appear appropriate error.
Thanks!