for new UUIDs #507

New issue

Closed

opened 2026-02-25 23:42:42 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:42:42 +03:00

Owner

Originally created by @lukastribus on GitHub (Sep 19, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/705

Hello,

I just created a new check/UUID, a few successful log entries are already in there.

Going to:

https://healthchecks.io/checks/<UUID>/details/

shows everything is fine.

However clicking on "show more" (the new filter interface) leads to a long running transaction that after 30 seconds times out with a 502 Bad Gateway ("service down, please try in 10 minutes"):

https://healthchecks.io/checks/<UUID>/log/

I'm assuming the new interface may be trying to access historic data that is not there yet. Not sure if the backend is busy looping.

This is on the hosted healthchecks.io instance.

Thank you!
Lukas

Originally created by @lukastribus on GitHub (Sep 19, 2022). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/705 Hello, I just created a new check/UUID, a few successful log entries are already in there. Going to: https://healthchecks.io/checks/<UUID>/details/ shows everything is fine. However clicking on "show more" (the new filter interface) leads to a long running transaction that after 30 seconds times out with a 502 Bad Gateway ("service down, please try in 10 minutes"): https://healthchecks.io/checks/<UUID>/log/ I'm assuming the new interface may be trying to access historic data that is not there yet. Not sure if the backend is busy looping. This is on the hosted `healthchecks.io` instance. Thank you! Lukas

kerem closed this issue

2026-02-25 23:42:42 +03:00

kerem commented

2026-02-25 23:42:42 +03:00

Author

Owner

@cuu508 commented on GitHub (Sep 19, 2022):

Hi Lukas, thanks for reporting this. I can reproduce the issue, looking into it.

@cuu508 commented on GitHub (Sep 19, 2022): Hi Lukas, thanks for reporting this. I can reproduce the issue, looking into it.

kerem commented

2026-02-25 23:42:42 +03:00

Author

Owner

@cuu508 commented on GitHub (Sep 19, 2022):

@lukastribus I've now deployed a fix which I think should fix the issue. Could you please test again?

@cuu508 commented on GitHub (Sep 19, 2022): @lukastribus I've now deployed a fix which *I think* should fix the issue. Could you please test again?

kerem commented

2026-02-25 23:42:42 +03:00

Author

Owner

@lukastribus commented on GitHub (Sep 20, 2022):

It works for me now, thank you!

@lukastribus commented on GitHub (Sep 20, 2022): It works for me now, thank you!

kerem referenced this issue

2026-02-26 00:30:18 +03:00

[PR #507] [CLOSED] [Snyk] Security upgrade django from 1.11.29 to 2.2.21 #979