Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Invalid exception: Field has an invalid range
See original GitHub issueThe change introduced in the version 1.8.0 introduces breaking changes that are not compatibles with the expected behaviour in the standard cron. (Cron Hour Range) .
If you write: "* * 9-20 * * *", then an exception is triggered: “Field (9-20) has an invalid range”.
The version 1.7.1 works fine. In version 1.8.0 or 1.8.1 if you modify the range to include the step it does not work either, i.e.: "* * 9-20/1 * * *", triggers: “Field (9-20/1) has an invalid range”.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I just pushed up v1.8.2. Please try it out and let me know if you’re still seeing issues. Thanks for reporting!
Awesome. Glad to hear it. Thanks!