Schedule without Schedule Type is running wild

Description

If a schedule is defined without schedule type it is running wild - the process is executed continuously.

I think this kind of schedule can be implemented better to run just one time on reboot.

Environment

None

Activity

Carlos Ruiz
May 16, 2024 at 9:11 AM

Yes - that sounds OK

zuhri utama
May 16, 2024 at 2:41 AM

hi , can we open new ticket and give more detail. i think we need to create migration script to add new list and change code to refer to new list for start on reboot. should we make the schedule type to be mandatory?

Carlos Ruiz
June 26, 2019 at 12:42 PM

Closing ticket - if required the suggestion from Nicolas, we can open a new ticket

Carlos Ruiz
June 26, 2019 at 12:41 PM
Carlos Ruiz
November 20, 2018 at 12:26 PM

Thanks .

I agree with your assessment.

I committed an initial fix at 7f7bf09 - this is just to avoid the CPU running wild on this misconfiguration.

I'll keep this ticket open to implement the complete solution as suggested by .

Regards,

Carlos Ruiz

Fixed

Details

Assignee

Reporter

Labels

Fix versions

Priority

Created November 19, 2018 at 12:50 PM
Updated May 19, 2024 at 9:01 AM
Resolved June 26, 2019 at 12:42 PM