Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grace period for START_TIME #910

Open
haikosaw opened this issue Oct 28, 2023 · 1 comment
Open

Grace period for START_TIME #910

haikosaw opened this issue Oct 28, 2023 · 1 comment
Labels

Comments

@haikosaw
Copy link

I looked around a bit but it didn´t seem like anyone spoke about this sort of thing yet.

Currently if I want to use the /start ping, the grace period dictates by what time a finish ping has to arrive. My use case would benefit from a distinction between a grace period for "job completion", and "job start".

I´m not sure what the best way would be of implementing such a thing, but what it would need to do is:

  • Send an alert if the task is not run within the start schedule (example 1 minute after schedule)
  • But also send alert when task is exceeding it's runtime (example grace configured for 1 hour, but no finish ping has come yet)
@cuu508 cuu508 added the feature label Dec 15, 2023
@cuu508 cuu508 changed the title [Feature] Grace period for START_TIME Grace period for START_TIME Dec 15, 2023
@moritzruth
Copy link

My use case for this would be a backup script that

  • runs every day at the same time (start grace time: 1min)
  • takes multiple hours to run (completion grace time: 6 hours)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants