[GH-ISSUE #461] Possible to specify a "run ID"? #348

New issue

Closed

opened 2026-02-25 23:42:07 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @jesobreira on GitHub (Dec 17, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/461

Hello,

I'm using the service and all I can say is that it works pretty good!

I was wondering if it's possible to specify a "run ID"... Something like:

https://hc-ping.com/00000000-0000-0000-0000-000000000000/start/<run ID>

I have some cronjobs that can overlap (i.e. they are set for an interval but they might - by purpose - run even if the previous run hasn't finished yet) and I would like to see the running time of each task. In the current behavior, the check gets a little confused once one of the tasks declares that it finished running.

Is it possible currently?

Thank you!

Originally created by @jesobreira on GitHub (Dec 17, 2020). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/461 Hello, I'm using the service and all I can say is that it works pretty good! I was wondering if it's possible to specify a "run ID"... Something like: > https://hc-ping.com/00000000-0000-0000-0000-000000000000/start/<run ID\> I have some cronjobs that can overlap (i.e. they are set for an interval but they might - by purpose - run even if the previous run hasn't finished yet) and I would like to see the running time of each task. In the current behavior, the check gets a little confused once one of the tasks declares that it finished running. Is it possible currently? Thank you!

kerem

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

closed this issue
added the
question
label

kerem commented

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

Author

Owner

@cuu508 commented on GitHub (Aug 27, 2021):

There's #319 about adding optional idempotence ("run ID") key to ping requests. Each ping's idempotence key would need to be stored in the database. In principle, it would then be possible to calculate run times for overlapping jobs.

I'm closing this issue as a duplicate.

@cuu508 commented on GitHub (Aug 27, 2021): There's #319 about adding optional idempotence ("run ID") key to ping requests. Each ping's idempotence key would need to be stored in the database. In principle, it would then be possible to calculate run times for overlapping jobs. I'm closing this issue as a duplicate.