I dont think this is documented, but saw in other threads since 2.2.2.5 still only 100 calls per minute for intent/site API. I am not sure you can overcome this or handle this better with the SDK, one way could be to monitor the progress of the "get_task_tree" is to use a loop that checks the status of the task at regular intervals until it is completed. You can use the `get_task_by_id` method to check the status of the task and then use a conditional statement to determine if the task is completed or not. If the task is not completed, you can use the `time.sleep` method to add a delay before checking the status again.
The rate limiter provided by the DNAC SDK, it is designed to help prevent your script from exceeding the rate limits set by Cisco Catyst Center. If your script exceeds the rate limit, the SDK will automatically retry the request after a certain amount of time has passed. This means that you do not need to worry about adding delays between each addition as the SDK will handle this for you.
It's a good practice to implement exponential backoff and retry mechanisms in your application to handle any potential rate limiting issues. This will help your application to automatically adjust its request rate based on the API's response.
I guess if this does not help, the TAC would be your next call.
Hope this helps.
Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io
