GeoffO Posted September 21, 2018 Share Posted September 21, 2018 We're running v8.4, Build 8459. We have discovery jobs set to run at specific times (e.g. "Weekly - 01:00"). When running an on-demand discovery, the job's schedule is changed to one minute in the future and the frequency is reset to daily (see example). My feature request: Ability to run on-demand jobs without affecting the previously established schedule. I mean, the workarounds are to create a new discovery job as a one-off, or go back and update the schedule after. Neither is particularly desirable. It would be great if we could run on-demand discoveries while not affecting the defined schedule--or even as a compromise, could the ad-hoc job at least maintain/honor the defined frequency (daily/weekly/etc)? Thanks. -Geoff Link to comment Share on other sites More sharing options...
support Posted September 22, 2018 Share Posted September 22, 2018 Thanks for your request Geoff. The reason we change this is because the Windows Service triggers this of the schedule, so the only way currently to 'Run The Discovery Job Now', is to change the schedule. We'll look to see if we can modify this so that schedule is restored after the job is run, or possible some other method we can think of. Regards Click Studios Link to comment Share on other sites More sharing options...
DavidRa Posted January 17, 2019 Share Posted January 17, 2019 +1 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.