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
Report Error "Invalid Range Type." - Microsoft Dynamics AX ...
I have recently created a report that was working fine. Only recently when users are trying to access the report the are facing...
Read more >Elasticsearch exception (failed to create query: invalid range
I have a query for finding all record witch ...
Read more >Handle API errors | Google Calendar
This can mean that a required field or parameter has not been provided, the value supplied is invalid, or the combination of provided...
Read more >Platform error codes | ArcGIS Maps SDK for .NET
ArcGIS Runtime error Invalid access range Feature service is not loaded, it needs to be loaded before passed into the sync task. Check...
Read more >Proposed Error message describes invalid form field value
Each test target either has no form field error indicators, ... such as an invalid password; input not in an expected format, expected...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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!