<?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: Scheduled PDF delivery not being received -  Invalid earliest_time in python.log in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128255#M2901</link>
    <description>&lt;P&gt;Has this already been fixed? I just stumbled over this error in v6.2.6. A scheduled report is generating a pdf dashboard, where the panels used inline searches with tokenized $earliest$ and $latest$. Replacing the tokens helped. &lt;/P&gt;</description>
    <pubDate>Tue, 08 Dec 2015 17:41:01 GMT</pubDate>
    <dc:creator>Olli1919</dc:creator>
    <dc:date>2015-12-08T17:41:01Z</dc:date>
    <item>
      <title>Scheduled PDF delivery not being received -  Invalid earliest_time in python.log</title>
      <link>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128253#M2899</link>
      <description>&lt;P&gt;Scheduled PDF delivery not being received -  Invalid earliest_time in python.log &lt;/P&gt;

&lt;P&gt;Exception raised while trying to prepare "REPORT - Example" for rendering to PDF. No search job available for view that requires search job &lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2015 16:55:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128253#M2899</guid>
      <dc:creator>rsimmons</dc:creator>
      <dc:date>2015-02-05T16:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduled PDF delivery not being received -  Invalid earliest_time in python.log</title>
      <link>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128254#M2900</link>
      <description>&lt;P&gt;This is a known issue where the time range with token should not be inserted using Viz Editor/XML, it has been address in a later release.&lt;/P&gt;

&lt;P&gt;workaround: &lt;BR /&gt;
This issue can be resolve by removing  &lt;/P&gt;

&lt;P&gt;$earliest$&lt;BR /&gt;
      &lt;LATESTTIME&gt;$latest$&lt;/LATESTTIME&gt;&lt;/P&gt;

&lt;P&gt;from the XML&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2015 17:02:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128254#M2900</guid>
      <dc:creator>rsimmons</dc:creator>
      <dc:date>2015-02-05T17:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduled PDF delivery not being received -  Invalid earliest_time in python.log</title>
      <link>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128255#M2901</link>
      <description>&lt;P&gt;Has this already been fixed? I just stumbled over this error in v6.2.6. A scheduled report is generating a pdf dashboard, where the panels used inline searches with tokenized $earliest$ and $latest$. Replacing the tokens helped. &lt;/P&gt;</description>
      <pubDate>Tue, 08 Dec 2015 17:41:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Scheduled-PDF-delivery-not-being-received-Invalid-earliest-time/m-p/128255#M2901</guid>
      <dc:creator>Olli1919</dc:creator>
      <dc:date>2015-12-08T17:41:01Z</dc:date>
    </item>
  </channel>
</rss>

