-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
11.2.0
-
None
-
11.02
-
Severity 3 - Minor
-
Issue Summary
Trying to save invalid cron schedule resets the input
Steps to Reproduce
- Go to Database integrity checks
- Type bad cron
- Try to save
Expected Results
Message is present but the value remains the sam
Actual Results
Old value is used
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available