Facing "context deadline exceeded (Client.Timeout exceeded while awaiting headers)" errors

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Facing "context deadline exceeded (Client.Timeout exceeded while awaiting headers)" errors

L0 Member

I’m trying to fetch Accounts, Safes, and Safe Members data in parallel using the CyberArk APIs.

For all requests, I’ve set the limit to 1000 and a timeout of 10 minutes.

 

Initially, we were hitting the ITACM040S error, which we resolved by enabling concurrentSession during authentication. However, we’re now seeing context deadline exceeded (Client.Timeout exceeded while awaiting headers) errors specifically for the Safes API, while the Accounts API responses are coming back successfully.

 

I came across an official CyberArk GitHub script where the timeout is set to 45 minutes, which feels quite high for practical usage:

https://github.com/cyberark/epv-api-scripts/blob/main/Get%20Accounts/Get-Accounts.ps1

 

I’m trying to understand:

 

  • Is this timeout issue related to requesting a limit of 1000 records for the Safes API?
  • Is increasing the client timeout the expected approach here?
  • Is this a role related issue? We have provided the "Auditor" role to the user. Ans user type is "BasicUser"
  • Are there any documented or recommended upper limits, pagination strategies, or timeout best practices specifically for fetching Safes data?

 

I couldn’t find clear documentation around this and would appreciate insights or best practices from the community.

0 REPLIES 0
  • 385 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!