<?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 Facing &amp;quot;context deadline exceeded (Client.Timeout exceeded while awaiting headers)&amp;quot; errors in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/facing-quot-context-deadline-exceeded-client-timeout-exceeded/m-p/1422244#M88998</link>
    <description>&lt;P&gt;I’m trying to fetch &lt;B&gt;Accounts, Safes, and Safe Members&lt;/B&gt; data in parallel using the CyberArk APIs.&lt;/P&gt;&lt;P&gt;For all requests, I’ve set the &lt;B&gt;limit to 1000&lt;/B&gt; and a &lt;B&gt;timeout of 10 minutes&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Initially, we were hitting the &lt;B&gt;ITACM040S&lt;/B&gt; error, which we resolved by enabling &lt;B&gt;concurrentSession&lt;/B&gt; during authentication. However, we’re now seeing &lt;B&gt;context deadline exceeded (Client.Timeout exceeded while awaiting headers)&lt;/B&gt; errors specifically for the &lt;B&gt;Safes API&lt;/B&gt;, while the &lt;B&gt;Accounts API&lt;/B&gt; responses are coming back successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came across an official CyberArk GitHub script where the timeout is set to &lt;B&gt;45 minutes&lt;/B&gt;, which feels quite high for practical usage:&lt;/P&gt;&lt;P&gt;https://github.com/cyberark/epv-api-scripts/blob/main/Get%20Accounts/Get-Accounts.ps1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m trying to understand:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is this timeout issue related to requesting a &lt;B&gt;limit of 1000&lt;/B&gt; records for the Safes API?&lt;/LI&gt;&lt;LI&gt;Is increasing the client timeout the expected approach here?&lt;/LI&gt;&lt;LI&gt;Is this a role related issue? We have provided the "Auditor" role to the user. Ans user type is "BasicUser"&lt;/LI&gt;&lt;LI&gt;Are there any documented or recommended &lt;B&gt;upper limits, pagination strategies, or timeout best practices&lt;/B&gt; specifically for fetching Safes data?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I couldn’t find clear documentation around this and would appreciate insights or best practices from the community.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2026 06:10:47 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-01-19T06:10:47Z</dc:date>
    <item>
      <title>Facing "context deadline exceeded (Client.Timeout exceeded while awaiting headers)" errors</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/facing-quot-context-deadline-exceeded-client-timeout-exceeded/m-p/1422244#M88998</link>
      <description>&lt;P&gt;I’m trying to fetch &lt;B&gt;Accounts, Safes, and Safe Members&lt;/B&gt; data in parallel using the CyberArk APIs.&lt;/P&gt;&lt;P&gt;For all requests, I’ve set the &lt;B&gt;limit to 1000&lt;/B&gt; and a &lt;B&gt;timeout of 10 minutes&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Initially, we were hitting the &lt;B&gt;ITACM040S&lt;/B&gt; error, which we resolved by enabling &lt;B&gt;concurrentSession&lt;/B&gt; during authentication. However, we’re now seeing &lt;B&gt;context deadline exceeded (Client.Timeout exceeded while awaiting headers)&lt;/B&gt; errors specifically for the &lt;B&gt;Safes API&lt;/B&gt;, while the &lt;B&gt;Accounts API&lt;/B&gt; responses are coming back successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came across an official CyberArk GitHub script where the timeout is set to &lt;B&gt;45 minutes&lt;/B&gt;, which feels quite high for practical usage:&lt;/P&gt;&lt;P&gt;https://github.com/cyberark/epv-api-scripts/blob/main/Get%20Accounts/Get-Accounts.ps1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m trying to understand:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is this timeout issue related to requesting a &lt;B&gt;limit of 1000&lt;/B&gt; records for the Safes API?&lt;/LI&gt;&lt;LI&gt;Is increasing the client timeout the expected approach here?&lt;/LI&gt;&lt;LI&gt;Is this a role related issue? We have provided the "Auditor" role to the user. Ans user type is "BasicUser"&lt;/LI&gt;&lt;LI&gt;Are there any documented or recommended &lt;B&gt;upper limits, pagination strategies, or timeout best practices&lt;/B&gt; specifically for fetching Safes data?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I couldn’t find clear documentation around this and would appreciate insights or best practices from the community.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 06:10:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/facing-quot-context-deadline-exceeded-client-timeout-exceeded/m-p/1422244#M88998</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-01-19T06:10:47Z</dc:date>
    </item>
  </channel>
</rss>

