Sergey Odinokov

@pieceofsummer, I've added the corresponding feature request, please see https://github.com/HangfireIO/Hangfire/issues/1044.

Please specify `CronFormat.IncludeSeconds` in the constructor, otherwise it's unclear in general case whether 6th part is about seconds or about years. ```csharp var expression = CronExpression.Parse("0 0 11 * 7...

Yeah, sounds as a great addition. Need to change the [grammar first](https://github.com/HangfireIO/Cronos#cron-grammar) and then make the according changes to the code, it will be much easier (than changing the grammar)....

Unfortunately this problem relates to the format itself, please see [this section on Wikipedia](https://en.wikipedia.org/wiki/Cron#Non-standard_characters): > Note that frequencies in general cannot be expressed; only step values which evenly divide their...

Please describe the idea behind this feature – we need to understand when it's required, because usually we are iterating forward.

Thanks everyone for your considerations and detailed descriptions. I've also re-checked other implementation like `CronExpression` in Quartz.NET (it has `GetTimeBefore` method but it's [not implemented](https://github.com/quartznet/quartznet/blob/main/src/Quartz/CronExpression.cs#L2164-L2168)) and NCrontab and together with...

The `* * * * * *` expression is ambiguous – some parsers treat the first part as a second value, other parsers treat the first part as a minute,...

Maybe years will be added, may be not (I don't see any useful use case for them, but let's wait and see), but in general case (with years), reliable automatic...

Not a problem, I'm just trying to avoid ambiguities as much as possible, because completely tired of them😳.

Cronos wasn't planned to calculate occurrences after 2099 year, there's a hardcoded values, please see the following snippet. Such an upper bound is required, because it's not possible to know...