Skip to content
TORNLIFE More

503 errors causing chains to drop

Started by Harley [258120] Wiki Contributor on in Bugs & Issues.

21 replies · 223 views · thread synced · 5 days ago · View on torn.com
About this thread

Posts archived: 22 / 22 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
22
Discussion span
→
Authority score
61 / 100
Historical score
39 / 100
Story score
47 / 100
Engagement score
63 / 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

Mentioned in this thread

Coral [350465] ×1 Ryosuki [1194157] ×1 CastleQueen [1735522] ×1 BlackIC2 [1825387] ×1 Icydraft [2031301] ×1

Harley [258120] Wiki Contributor

I seem to remember a bug report recently where chains were reinstated where they were left of, we just had two chains die around 20, that's 40 hits wasted. Is it possible this could be reinstated again?


aurel1 [1046304] Admin Staff

Are you sure, that it was exactly error 503 (not 504)? What exactly happened, fight timed out? When exactly this happened, on your first turn or later? Have you tried to refresh the page?
Harley [258120] Wiki Contributor

I'm most definitely sure that was the error I saw, first the cloudfare page, then the blank screen with 503.

first timed out chain happened after this:

29/07/1712:45:19 PMCastleQueen attacked Ryosuki but timed out

Second time out happened between these two attacks:

Mentions: BlackIC2 [1825387] · CastleQueen [1735522] · Coral [350465] · Icydraft [2031301] · Ryosuki [1194157]

JussiJernkuuk [1874922]

Yeah I saw 503/Cloudflare too.

Just curious though, how do you even reinstate a chain? An admin just starts it again where it dropped off and hopes that someone is around to pick it up?