Skip to content
TORNLIFE More

Chain Timer being reported wrong on API

Started by sicko [2682050] on in Bugs & Issues.

8 replies · 88 views · thread synced · 5 days ago · View on torn.com
About this thread

Posts archived: 9 / 9 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
9
Discussion span
→
People posting
6
Likes on archived posts
16
Posts by staff, officers and moderators
3
Authority score
57 / 100
Historical score
40 / 100
Story score
53 / 100
Engagement score
56 / 100

Most-liked replies

  • splent [2088243] Admin · 3 likes ·
    Hey, Just letting you know we're currently investigating the issue. It looks like there's a DB replica lag which might need some optimization, but we first need to determine a cause, so it's a process that might take some time. …
  • splent [2088243] Admin · 1 likes ·
    I'm closing this bug since the issue was fixed since (DB replica lag). Thanks!
  • CloudJumper [1636201] · 1 likes ·
    Passing along to Mauro. Thanks..!!
sicko [2682050] · #1 · edited

My faction is currently completing a chain and over the last half hour the chain timer has gotten completely out of sync as reported by the API. This has been evident through the use of the chaining function on TornPDA (iPhone & iPad) and the YATA and Tornium discord bots as they are both now reporting that the chain is in cooldown however it has not dropped below 3 minutes.

 

This was a gradual process as it started resetting back to lower values when they should have been 5.00 and now is in cooldown. The Chain # has been updating the entire time, just a bit slow. To be clear the API is updating the chain hits and saying the chain is over at the same time.

 

[image: i.gyazo.com]

 

[image: i.gyazo.com]

 

[image: i.gyazo.com]

 

 

 

 

[image: i.gyazo.com]

 

[image: i.gyazo.com]

 

 

As of 1730 TCT the API seems to be giving correct values again, it was also a gradual change back to normal

 

As of 2205 TCT is has began to do the same thing again

lonerider543 [2173471] · #2 · edited

Just to confirm, API is spitting out nonsense values for the timeout/cooldown/modifier. The actual 'current' figure still goes up properly.

 

 

Started about 30 minutes ago when we got alerts from various sources that the chain was about to timeout when people were still making hits every few seconds.

 

 

Edit: just to report back that it appears to be fixed.

BadZena [1968552] · #4

Having the same issues, started last night, seemed to settle, was still being loopy this morning, then settled, but now back to being loopy again...

 

It is starting to annoy, somewhat.  Its kinda like the 'Boy who cried Wolf'...

splent [2088243] Admin Staff · #7

Hey, 

 

Just letting you know we're currently investigating the issue. It looks like there's a DB replica lag which might need some optimization, but we first need to determine a cause, so it's a process that might take some time. 

Thanks everyone for feedback - it's helpful to pin-point exact times in order to check the logs. 

Thanks!