<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: what format should cron be when setting up a schedule in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/what-format-should-cron-be-when-setting-up-a-schedule/m-p/276181#M5084</link>
    <description>&lt;P&gt;Hi HattrickNZ,&lt;/P&gt;

&lt;P&gt;well, have you tried to use &lt;CODE&gt;'&lt;/CODE&gt; or &lt;CODE&gt;"&lt;/CODE&gt; in the cron field? &lt;BR /&gt;
If you do so, you will get this error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Encountered the following error while trying to save: In handler 'savedsearch': Invalid cron_schedule="'* 5 * * *'"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So, the answer is: No quotes of any kind are needed in the cron entry field.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Wed, 06 Apr 2016 03:41:54 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2016-04-06T03:41:54Z</dc:date>
    <item>
      <title>what format should cron be when setting up a schedule</title>
      <link>https://community.splunk.com/t5/Alerting/what-format-should-cron-be-when-setting-up-a-schedule/m-p/276180#M5083</link>
      <description>&lt;P&gt;sorry forthis simplistic question I just can't work it out from the instructions.&lt;/P&gt;

&lt;P&gt;here I want to set up a cron job to run every day at 3:03 a.m.&lt;/P&gt;

&lt;P&gt;when seeting up a cron job(see pic beow) what format should the paramter be in in the input box below in the pic:&lt;BR /&gt;
1 - no quotes&lt;BR /&gt;
03 3 * * *&lt;BR /&gt;
2 - single quotes &lt;BR /&gt;
'03 3 * * *'&lt;BR /&gt;
3 - other single quotes forget the name&lt;BR /&gt;
&lt;CODE&gt;03 3 * * *&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/1201i95EDB4F7D94C5FE1/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 03:36:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/what-format-should-cron-be-when-setting-up-a-schedule/m-p/276180#M5083</guid>
      <dc:creator>HattrickNZ</dc:creator>
      <dc:date>2016-04-06T03:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: what format should cron be when setting up a schedule</title>
      <link>https://community.splunk.com/t5/Alerting/what-format-should-cron-be-when-setting-up-a-schedule/m-p/276181#M5084</link>
      <description>&lt;P&gt;Hi HattrickNZ,&lt;/P&gt;

&lt;P&gt;well, have you tried to use &lt;CODE&gt;'&lt;/CODE&gt; or &lt;CODE&gt;"&lt;/CODE&gt; in the cron field? &lt;BR /&gt;
If you do so, you will get this error:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Encountered the following error while trying to save: In handler 'savedsearch': Invalid cron_schedule="'* 5 * * *'"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;So, the answer is: No quotes of any kind are needed in the cron entry field.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 03:41:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/what-format-should-cron-be-when-setting-up-a-schedule/m-p/276181#M5084</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-04-06T03:41:54Z</dc:date>
    </item>
  </channel>
</rss>

