<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scheduling on Step Documentation</title>
    <link>https://step.dev/knowledgebase/31/categories/scheduling/</link>
    <description>Recent content in Scheduling on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 29 Nov 2020 14:08:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/31/categories/scheduling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Execution Subscriptions</title>
      <link>https://step.dev/knowledgebase/31/userdocs/alerting-notifications/subscriptions/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/alerting-notifications/subscriptions/</guid>
      <description>From a user&amp;rsquo;s perspective, it is often useful to be notified about certain events, like the execution (or failure) of particular plans. This is possible by leveraging the functionality of the Alerting Rules and Notifications.
Expert users can create the corresponding rules themselves, however this is not necessarily a straightforward task, and figuring out the exact definitions may be cumbersome. Therefore, Step provides a simple Wizard which allows to set up notifications in an easy way.</description>
    </item>
    
    <item>
      <title>Schedules</title>
      <link>https://step.dev/knowledgebase/31/userdocs/schedulerview/</link>
      <pubDate>Sun, 29 Nov 2020 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/schedulerview/</guid>
      <description>Schedules allow to configure the recurring or one-time execution of Plans, enabling automated, time-based workflow execution for tasks like synthetic monitoring and beyond.
For the schedules to work correctly, ensure to properly set up the controller’s machine timezone before you start it. Description Let’s describe the Step schedules view: You can access it by clicking “Schedules” on the sidebar menu:
Here is the column description:
Name (1): the name of the schedule.</description>
    </item>
    
    <item>
      <title>Scheduled execution reporting</title>
      <link>https://step.dev/knowledgebase/31/userdocs/executions/schedule-executions-reporting/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/executions/schedule-executions-reporting/</guid>
      <description>In this view, you can find reports aggregated across multiple executions of the same schedule. The main purpose of this view is to provide insights into whether scheduled executions have passed or failed over time.
Schedule Name – The name of the scheduled task. Use quick-actions to configure the associated plan or schedule. Last Execution – The most recent time the schedule was executed and its result (pass/fail). The settings for automatic refresh and the time range to be shown.</description>
    </item>
    
  </channel>
</rss>
