Discovery Schedules showing wrong next action date in sys_trigger tableIssue Customer has automation through which the discovery schedule created automatically from catalog item. It is working fine however when we see the next run time on sys_trigger table it is showing year 2076. When we manually create the discovery schedule it set correct date and time in sys_trigger table. Discovery schedules show wrong next action date in sys_trigger table.CauseSomehow "Time" (run_time field) has bad value.ResolutionSomehow "Time" (run_time field) has bad value. Do clear this field save and then change the field to appropriate value. Remove the value on time field and save it and then again change the field to appropriate value and check if it shows the correct value in now sys_trigger table.