Replies: 1 comment
-
And not to sidetrack this particular discussion, but I would actually like to have a way to intentionally set something on the job scheduler where it would be "disabled" but preserve everything about the schedule/data/template/etc. So a bit of the reverse of the original questions, but any answer could provide enlightenment for both of us. Looking for options, I did a cursory look through the job scheduler code and saw that if endData was set artificially in the past or if the max iteration count was set to less than the current iteration count, the upsert would no-op. So those didn't seem like good options for me. But wondering if there is another workaround? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Looking into using the newer job schedulers and wondering how it works when you have a job scheduler that repeats but has an option to end on a date or after a certain number of jobs. Does that job scheduler remain in the system after the end date or number is reached? If so, does that use system resources?
Beta Was this translation helpful? Give feedback.
All reactions