<?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 We are experiencing a problem, data may not be up to date. Please try again in a few minutes. in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/we-are-experiencing-a-problem-data-may-not-be-up-to-date-please/m-p/1242231#M8877</link>
    <description>&lt;P&gt;&lt;!--StartFragment --&gt;&lt;/P&gt;
&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I've been seeing the following message on our Cortex XDR Dashboard for the past few days:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"We are experiencing a problem, data may not be up to date. Please try again in a few minutes."&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There's also a link to &lt;EM&gt;Download support file&lt;/EM&gt; included.&lt;/P&gt;
&lt;P&gt;Has anyone else encountered this issue or have any insights into what might be causing it?&lt;/P&gt;
&lt;P&gt;Thank you.&lt;!--EndFragment --&gt;&lt;/P&gt;
&lt;P&gt;JO&lt;/P&gt;</description>
    <pubDate>Wed, 19 Nov 2025 19:42:01 GMT</pubDate>
    <dc:creator>Juliortega</dc:creator>
    <dc:date>2025-11-19T19:42:01Z</dc:date>
    <item>
      <title>We are experiencing a problem, data may not be up to date. Please try again in a few minutes.</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/we-are-experiencing-a-problem-data-may-not-be-up-to-date-please/m-p/1242231#M8877</link>
      <description>&lt;P&gt;&lt;!--StartFragment --&gt;&lt;/P&gt;
&lt;P&gt;Hello All,&lt;/P&gt;
&lt;P&gt;I've been seeing the following message on our Cortex XDR Dashboard for the past few days:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"We are experiencing a problem, data may not be up to date. Please try again in a few minutes."&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There's also a link to &lt;EM&gt;Download support file&lt;/EM&gt; included.&lt;/P&gt;
&lt;P&gt;Has anyone else encountered this issue or have any insights into what might be causing it?&lt;/P&gt;
&lt;P&gt;Thank you.&lt;!--EndFragment --&gt;&lt;/P&gt;
&lt;P&gt;JO&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 19:42:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/we-are-experiencing-a-problem-data-may-not-be-up-to-date-please/m-p/1242231#M8877</guid>
      <dc:creator>Juliortega</dc:creator>
      <dc:date>2025-11-19T19:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: We are experiencing a problem, data may not be up to date. Please try again in a few minutes.</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/we-are-experiencing-a-problem-data-may-not-be-up-to-date-please/m-p/1244993#M8964</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/136012"&gt;@Juliortega&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day, and Apologies for the delay in responding.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The error message &lt;STRONG&gt;“We are experiencing a problem, data may not be up to date. Please try again in a few minutes”&lt;/STRONG&gt; is a generic notification in the &lt;STRONG&gt;Cortex XDR / XSIAM&lt;/STRONG&gt; console indicating that the user interface (UI) is temporarily unable to retrieve or synchronize data with backend services.&lt;/P&gt;
&lt;H3&gt;Common Causes:&lt;/H3&gt;
&lt;P&gt;Based on internal case history and engineering findings, this issue may occur due to the following reasons:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Backend Software Defects or Regressions:&lt;/STRONG&gt;&lt;BR /&gt;This error is frequently observed after tenant upgrades (notably versions &lt;STRONG&gt;3.16&lt;/STRONG&gt; and &lt;STRONG&gt;4.3&lt;/STRONG&gt;), where a defect in the dashboard rendering engine or management API prevents the UI from retrieving dashboard metadata.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Database Connectivity Issues:&lt;/STRONG&gt;&lt;BR /&gt;Failures in communication between the tenant database and the dashboard engine can cause this banner to appear for all users.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Resource Saturation:&lt;/STRONG&gt;&lt;BR /&gt;High load or resource constraints on platform API services can lead to request timeouts, often resulting in &lt;STRONG&gt;HTTP 500 or 503&lt;/STRONG&gt; errors.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;User-Specific Configuration Issues:&lt;/STRONG&gt;&lt;BR /&gt;If the problem affects only a single user, it may be caused by a corrupted &lt;STRONG&gt;custom dashboard&lt;/STRONG&gt; that fails to load during login.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Multiple Browser Tabs:&lt;/STRONG&gt;&lt;BR /&gt;Making configuration changes in one browser tab can cause other open tabs to display this banner, indicating that their displayed data is outdated and requires a page refresh.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;H3&gt;Recommended Troubleshooting&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Standard Browser Cleanup:&lt;/STRONG&gt;&lt;BR /&gt;Clear browser cache and cookies, or access the console using a &lt;STRONG&gt;Private/Incognito&lt;/STRONG&gt; window to rule out stale cache or browser extension interference.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;P&gt;&lt;STRONG&gt;Diagnostic Data&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Support File:&lt;/STRONG&gt;&lt;BR /&gt;The link provided in the banner downloads a JSON file containing timestamps and a list of failed API calls. This information helps engineering identify which backend service is failing.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;HAR Logs:&lt;/STRONG&gt;&lt;BR /&gt;Capturing a HAR file while the dashboard fails to load often reveals &lt;STRONG&gt;HTTP 500 (Internal Server Error)&lt;/STRONG&gt; or &lt;STRONG&gt;HTTP 503 (Service Unavailable)&lt;/STRONG&gt; responses, commonly associated with the&lt;BR /&gt;&lt;CODE&gt;/api/webapp/dashboards/load_dashboards_list&lt;/CODE&gt; endpoint, which confirms a server-side issue.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;H3&gt;Recommendation:&lt;/H3&gt;
&lt;P&gt;The best course of action is to &lt;STRONG&gt;create a support ticket at the time the issue occurs&lt;/STRONG&gt;. This allows the support team to verify whether there is an ongoing outage or a known backend issue and enables the engineering team to address the problem immediately if required.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;"mark this as a Solution".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Happy New Year!!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 20:30:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/we-are-experiencing-a-problem-data-may-not-be-up-to-date-please/m-p/1244993#M8964</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-01-06T20:30:50Z</dc:date>
    </item>
  </channel>
</rss>

