Recurring checks, like finding task records that are unassigned, are implemented using platform automation that runs on a schedule. ServiceNow provides two common development-aligned places for this type of logic. Scheduled Script Execution is a scheduled job mechanism that runs server-side scripts at defined intervals. Developers use it to query tables (such as Task) and take actions like updating fields, creating follow-up records, or sending notifications when conditions are met. This matches option C. For low-code automation, Flow Designer also supports scheduled triggers, allowing developers to run a flow at specific times or on a repeating schedule to perform checks and actions. This matches option A (Scheduled Flows). Discovery Schedules are specific to the Discovery feature set for scanning infrastructure and are not used for general task management checks. “System Schedules” is not the standard construct where custom recurring business logic is authored for application development; the platform’s scheduled logic is typically implemented through scheduled jobs (including script executions) and scheduled flow triggers.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit