# Error 429 Too Many Requests with CloudQuery Azure Storage configuration

**URL:** <https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648>\
**Category:** CloudQuery Plugins\
**Created:** [October 19, 2023, 12:12pm UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648 "2023-10-19T12:12:51Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![calm-walrus](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@calm-walrus](https://community.cloudquery.io/u/calm-walrus)\
**Post date:** [October 19, 2023, 12:12pm UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/1 "2023-10-19T12:12:51Z")

</div>

I have played around with the `spec.concurrency` and `scheduler: "round-robin"`, but I still can’t pass this error 429:

```auto
ERR table resolver finished with error error="GET https://management.azure.com/subscriptions/xxx/resourceGroups/rg/providers/Microsoft.Storage/storageAccounts/sa/blobServices/default/containers\n--------------------------------------------------------------------------------\nRESPONSE 429: 429 Too Many Requests\nERROR CODE: TooManyRequests\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"TooManyRequests\",\n \"message\": \"The request is being throttled as the limit has been reached for operation type - List_ObservationWindow_00:05:00. For more information, see - https://aka.ms/srpthrottlinglimits\"\n }\n}\n--------------------------------------------------------------------------------\n" client=subscriptions/xxx module=azure-src table=azure_storage_containers

```

I read the mentioned document, [Azure Subscription Service Limits](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-storage-resource-provider-limits). I do see the list limits on storage accounts: only 100 per 5 minutes.

```auto
Storage account management operations (list) - 100 per 5 minutes

```

How can I adjust the source configuration to pass this issue?

---

<div class="post-metadata">

**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\
**Post date:** [October 19, 2023, 12:16pm UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/2 "2023-10-19T12:16:07Z")

</div>

Hi @calm-walrus,

I’m currently working on exposing the Azure Go SDK settings so one could configure the retries.

You can subscribe to [this issue](https://github.com/cloudquery/cloudquery/issues/11225).

I’ll close that issue once the fix is done.

---

<div class="post-metadata">

**Author:** ![calm-walrus](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@calm-walrus](https://community.cloudquery.io/u/calm-walrus)\
**Post date:** [October 19, 2023, 12:19pm UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/3 "2023-10-19T12:19:47Z")

</div>

Yes, that’s the same issue, thanks.  
@erez I saw [this issue](https://github.com/cloudquery/cloudquery/issues/11225) has been closed with a PR merged.

What’s the meaning?

Do I need to install a new version of `cloudquery` command line?

---

<div class="post-metadata">

**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\
**Post date:** [October 20, 2023, 10:14am UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/4 "2023-10-20T10:14:45Z")

</div>

I’ll release a new Azure plugin version in a bit for you to try:

[https://github.com/cloudquery/cloudquery/pull/14766](https://github.com/cloudquery/cloudquery/pull/14766) this one.

---

<div class="post-metadata">

**Author:** ![calm-walrus](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@calm-walrus](https://community.cloudquery.io/u/calm-walrus)\
**Post date:** [October 20, 2023, 10:15am UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/5 "2023-10-20T10:15:23Z")

</div>

ic. Sure. I’ll wait for it.

---

<div class="post-metadata">

**Author:** ![calm-walrus](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@calm-walrus](https://community.cloudquery.io/u/calm-walrus)\
**Post date:** [October 20, 2023, 11:49pm UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/6 "2023-10-20T23:49:44Z")

</div>

@erez

I have switched to use the latest Azure `azure@v10.1.0`, but I still got a lot of 429 errors.

```auto
RESPONSE 429: 429 Too Many Requests

```

---

<div class="post-metadata">

**Author:** ![erez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.cloudquery.io/erez/32/40_2.png) [@erez](https://community.cloudquery.io/u/erez)\
**Post date:** [October 21, 2023, 1:50pm UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/7 "2023-10-21T13:50:47Z")

</div>

Hi @calm-walrus, have you tried changing the default retry options? See [this link](https://www.cloudquery.io/docs/plugins/sources/azure/configuration#retry_options).

I would try a very high `max_retry_delay_seconds` for starters and also set `max_retries` and `retry_delay_seconds` to a higher value than the defaults.

---

<div class="post-metadata">

**Author:** ![calm-walrus](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@calm-walrus](https://community.cloudquery.io/u/calm-walrus)\
**Post date:** [October 23, 2023, 12:06am UTC](https://community.cloudquery.io/t/error-429-too-many-requests-with-cloudquery-azure-storage-configuration/648/8 "2023-10-23T00:06:45Z")

</div>

let me try

```yaml
retry_options:
  max_retries: 5
  try_timeout_seconds: 0
  retry_delay_seconds: 60
  max_retry_delay_seconds: 300

```
