John Roesler

Hi @Shawn-Huang-Tron, There is not currently any sort of retry logic supported in gocron. In general, I assume users today are handling any sort retry logic inside the job itself...

Here are the logs I get: Env: MacOS 12.4 on Apple M1 Docker: Engine: 20.10.17 VS Code: Version: 1.72.0 Commit: 64bbfbf67ada9953918d72e1df2f4d8e537d340e Date: 2022-10-04T23:19:55.212Z (6 days ago) Electron: 19.0.17 Chromium: 102.0.5005.167...

Hi @iangregsondev There isn’t support for this case exactly where you’re suggesting blocking overlapping schedules from being added. Could you share some additional details on the use case so perhaps...

Hi @iangregsondev interesting use case! This isn't supported today, but natively Cron can do things like run between periods. However, there is no way to lookup what the scheduled periods...

@aibotsoft this is interesting! The reason it is done the way currently is to allow checking the state of both the scheduler and individual job context states. The Acquire method...

@zerosoul13 looking into this some, I completely agree there is currently some lag between jobs that can cause a job to occur slightly later than expected. Definitely something we should...

@zerosoul13 could you test out the master branch when you have a chance and see if it's solved for you? I ran some jobs for several hours and had no...

I think having optionally enabled prometheus metrics could be a nice a feature to add.

Yeah. It'd be nice to make the metrics an interface so we can implement with prometheus now and then later it could be implemented with influx and others.

I’d also include the tags map, and the time timewrapper. Are you looking at implementing here? Another option besides creating a struct with exported fields is to implement the serialize...