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

Need a better way to track the execution of TimerJobs #1140

Closed
crossan007 opened this issue Oct 15, 2016 · 4 comments
Closed

Need a better way to track the execution of TimerJobs #1140

crossan007 opened this issue Oct 15, 2016 · 4 comments

Comments

@crossan007
Copy link
Contributor

TimerJobs currently store last exection time in a config setting. There should be a better way to track the previous runs of these jobs as we get more of them

@DawoudIO DawoudIO added this to the 2.3.0 milestone Oct 16, 2016
@DawoudIO
Copy link
Contributor

is this closed also

@crossan007
Copy link
Contributor Author

crossan007 commented Oct 16, 2016

No. This is for 2.4.0 unless i get really really ambitious

@DawoudIO DawoudIO modified the milestones: 2.4.0, 2.3.0 Oct 17, 2016
@DawoudIO DawoudIO removed this from the 2.4.0 milestone Nov 24, 2016
@crossan007 crossan007 modified the milestone: Backlog Jul 14, 2017
@DawoudIO DawoudIO removed this from the Backlog milestone Nov 1, 2023
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Jun 19, 2024
Copy link
Contributor

github-actions bot commented Aug 2, 2024

This issue was closed because it has been stalled for 15 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants