How to start/continue a Discovery Schedule "run after" sequence from the middle of that sequenceSummaryFor running several Discovery Schedules around the same time or day, best practice is to: Set a Max Runtime on the schedules, after having got a feel for how long they normally run forSchedule one of them to run at a set timeHave the rest of the schedules Run After that, in sequence.Set them all to run after 'even if cancelled', in case one does time out, it won't then break the sequence. There is a documented limitation to this though, which can be annoying when testing, or if you have to temporarily interrupt the discovery for any reason: https://docs.servicenow.com/en-US/bundle/utah-it-operations-management/page/product/it-operations-management/reference/discovery-schedule-run-options.html"This option is not valid when Discovery is started via DiscoverNow, or when using the Discover CI feature." That means you can not manually start the e.g. 6th schedule in the sequence with "Discover now" and expect 7th, 8th, 9th... schedules to run after. Only the schedule you Discover Now will run. The run after mechanism is implemented by a pair of Script Actions, both named "Discovery Run Next", triggered by discovery.complete and discovery.canceled events. These script actions deliberately don't do anything if the discovery_status record's description field has the value "Discover Now", which is what it will have if it was triggered by clicking Discover Now.InstructionsGiven that the Discovery Status [discovery_status] record's description of "Discover Now" is stopping it running any schedule set to run after this schedule, the workaround is to: Open the Discovery Schedule, that's in the middle of a sequenceClick the 'Discover now' related linkThat should redirect you to a list showing the Discovery Status - Open itChange the Description from "Discover Now" to "Scheduled", then Update Once this discovery status completes (or is cancelled), it will then trigger any schedules set to run after this one.