<?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>idea Allow pipeline and notebook refresh intervals shorter than 15 minutes (e.g., 5 minutes or less) in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/allow-pipeline-and-notebook-refresh-intervals/idi-p/1649945</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Currently, the minimum refresh interval for pipelines and notebooks in ArcGIS is &lt;STRONG&gt;15 minutes&lt;/STRONG&gt;. In many real-time or near-real-time use cases, this interval is too long.&lt;/P&gt;&lt;P&gt;For example, when monitoring &lt;STRONG&gt;live incident data, hazard feeds, IoT devices, or operational dashboards&lt;/STRONG&gt; used by emergency services and schools, having updates every 5 minutes (or even shorter if technically feasible) would make the system much more effective.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why this matters:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Critical decision-making often relies on data freshness. A 15-minute gap may mean missed opportunities for action.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Other platforms allow more granular scheduling, so reducing the minimum interval would align ArcGIS with user expectations for “live” data.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Even if shorter refreshes incur higher compute costs, giving administrators the &lt;STRONG&gt;flexibility to choose&lt;/STRONG&gt; is valuable. They can balance performance, cost, and operational needs.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Suggested improvement:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Reduce the minimum allowed refresh interval from 15 minutes to at least &lt;STRONG&gt;5 minutes&lt;/STRONG&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Ideally, provide flexibility to set custom intervals (e.g., every 1–5 minutes) depending on system performance and licensing.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This change would significantly improve ArcGIS usability for &lt;STRONG&gt;real-time dashboards, incident monitoring, and any workflows requiring near-live data feeds&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 12 Sep 2025 00:21:17 GMT</pubDate>
    <dc:creator>VictorJacobs</dc:creator>
    <dc:date>2025-09-12T00:21:17Z</dc:date>
    <item>
      <title>Allow pipeline and notebook refresh intervals shorter than 15 minutes (e.g., 5 minutes or less)</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/allow-pipeline-and-notebook-refresh-intervals/idi-p/1649945</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Currently, the minimum refresh interval for pipelines and notebooks in ArcGIS is &lt;STRONG&gt;15 minutes&lt;/STRONG&gt;. In many real-time or near-real-time use cases, this interval is too long.&lt;/P&gt;&lt;P&gt;For example, when monitoring &lt;STRONG&gt;live incident data, hazard feeds, IoT devices, or operational dashboards&lt;/STRONG&gt; used by emergency services and schools, having updates every 5 minutes (or even shorter if technically feasible) would make the system much more effective.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why this matters:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Critical decision-making often relies on data freshness. A 15-minute gap may mean missed opportunities for action.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Other platforms allow more granular scheduling, so reducing the minimum interval would align ArcGIS with user expectations for “live” data.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Even if shorter refreshes incur higher compute costs, giving administrators the &lt;STRONG&gt;flexibility to choose&lt;/STRONG&gt; is valuable. They can balance performance, cost, and operational needs.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Suggested improvement:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Reduce the minimum allowed refresh interval from 15 minutes to at least &lt;STRONG&gt;5 minutes&lt;/STRONG&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Ideally, provide flexibility to set custom intervals (e.g., every 1–5 minutes) depending on system performance and licensing.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This change would significantly improve ArcGIS usability for &lt;STRONG&gt;real-time dashboards, incident monitoring, and any workflows requiring near-live data feeds&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Sep 2025 00:21:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/allow-pipeline-and-notebook-refresh-intervals/idi-p/1649945</guid>
      <dc:creator>VictorJacobs</dc:creator>
      <dc:date>2025-09-12T00:21:17Z</dc:date>
    </item>
  </channel>
</rss>

