--- sourceDocument: Brazil IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Run options for discovery schedules # Run options for discovery schedules {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Run options for discovery schedules ServiceNow's discovery schedules support both horizontal and top-down discovery, offering flexible run options to control when and how discovery jobs execute. These options help you automate discovery based on your organizational needs and infrastructure changes. Show full answer Show less ## Run Options and Their Practical Use * **On Demand:** Default setting where discovery runs only when manually triggered with "Discover now." * **Daily:** Runs every day at a specified time, useful for frequent discovery updates. * **Weekly:** Runs on a designated day of the week at a specified time, allowing for scheduled weekly scans. * **Monthly:** Runs on a specific day each month at a set time. Note that if the selected day does not exist in a month (e.g., day 30 in February), the schedule skips that month. * **Periodically:** Runs repeatedly at defined intervals (days, hours, minutes, seconds) starting from a specified date/time. Unlike other options, the next run time is tracked in the Schedule \[systrigger\] table's Next Action field. * **Once:** Executes a single discovery at the specified starting date and time. * **Weekdays:** Runs every Monday through Friday at a chosen time, ideal for business hour scans. * **Weekends:** Runs every Saturday and Sunday at a set time, useful for minimizing impact during business hours. * **Month Last Day:** Runs on the last day of every month at the specified time, enabling end-of-month discovery. * **Calendar Quarter End:** Runs on quarter-end dates (March 31, June 30, September 30, December 31) at the specified time. Customization requires modifying the DiscoveryScheduleRunType script include. * **After Discovery:** Allows sequencing discovery schedules by running one after another finishes. You can specify whether to run even if the preceding discovery is canceled. This option does not work with DiscoverNow or Discover CI features and prevents loops or inactive schedules. ## Important Considerations * "Periodically" schedules require checking the Schedule \[systrigger\] table to verify next execution times. * The "After Discovery" option is useful for staggered discovery workflows but cannot be used to create scheduling loops or with manual triggers. * Customizing calendar quarter end dates requires scripting knowledge. * Schedules will not run if their criteria are not met---for example, monthly schedules on nonexistent days. ## Next Steps To implement or adjust discovery schedules, consider your organization's infrastructure update cycle and operational hours. Use the appropriate run option to balance discovery frequency with system impact. For orchestrated discovery workflows, leverage the "After Discovery" option to sequence scans effectively. Both horizontal and top-down discovery use these run options. {#discovery-schedule-run-options__table_qtt_ldf_br__entry__2} | Run option | Description | |-|-| | On Demand | Doesn't run on a schedule. Select Discover now to run Discovery. This is the default option. | | Daily | Runs every day. Use the Time field to specify the time of day. | | Weekly | Runs on one designated day of each week. Use the Time field to specify the time of day. | | Monthly | Runs on one designated day of each month. Use the Day field to select the day of the month. Use the Time field to specify the time of day. If the designated day doesn't occur in the month, the schedule doesn't run that month. For example, if you designate day 30, the schedule doesn't run in February. | | Periodically | Runs every designated time. Use the Repeat Interval field to define the time in days, hours, minutes, and seconds. The first Discovery runs at the point in time defined in the Starting field. The subsequent discoveries run after each Repeat Interval period passes. Note: For schedules configured as "Periodically", the "Time" column won't display the next scheduled run time. To determine the next execution time for schedule that is configured to run "Periodically", navigate to the Schedule \[sys_trigger\] table and locate the corresponding schedule record. The Next Action field will indicate the next scheduled run. | | Once | Run one time as designated by the date and time defined in the Starting field. | | Weekdays | Runs every Monday, Tuesday, Wednesday, Thursday, and Friday. Use the Time field to select the time of day. | | Weekends | Runs every Saturday and Sunday. Use the Time field to select the time of day. | | Month Last Day | Run the last day of every month. Use the Time field to select the time of day. | | Calendar Quarter End | Runs on March 31, June 30, September 30, and December 31. Use the Time field to select the time of day. To change the dates, modify the DiscoveryScheduleRunType script include. | | After Discovery | Allows you to sequentially stagger the schedule. Use this option to run this schedule after the Discovery designated in the Run after field finishes. Select the Even if canceled check box to designate that this discovery should run, even if the Run after Discovery is canceled before it finishes. * This option isn't valid when Discovery is started via DiscoverNow, or when using the Discover CI feature. * You can't designate an inactive Discovery schedule. * You can't create a loop by designating the run after Discovery to be the same Discovery. * This Discovery doesn't run if the Run after Discovery doesn't finish, with the exception that the Even if canceled check box is selected and the Discovery is canceled. {#discovery-schedule-run-options__ul_twl_ktt_wy} | [Table 1. Discovery schedule run options] {#discovery-schedule-run-options__table_qtt_ldf_br} **Related tasks** * [Schedule a top-down discovery by Service Mapping](https://www.servicenow.com/docs/UBOjz8AMUA_TfAK8aQSEEg "After Service Mapping discovers configuration items (CIs) belonging to your service instance for the first time, it then rediscovers CIs to find changes and updates. Create or modify discovery schedules to control how often Service Mapping rediscovers services or CIs. For example, you may create custom discovery schedules to avoid redundant stress on the infrastructure.") * [Schedule a horizontal discovery](https://www.servicenow.com/docs/A3BVdNwrtvD7FvMzmPuJVA#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.")