# Error 429 Too Many Requests when downloading azure\_consumption\_subscription\_legacy\_usage\_details

**URL:** <https://community.cloudquery.io/t/error-429-too-many-requests-when-downloading-azure-consumption-subscription-legacy-usage-details/252>\
**Category:** CloudQuery Plugins\
**Created:** [April 16, 2024, 11:28am UTC](https://community.cloudquery.io/t/error-429-too-many-requests-when-downloading-azure-consumption-subscription-legacy-usage-details/252 "2024-04-16T11:28:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![helping-crawdad](https://avatars.discourse-cdn.com/v4/letter/h/5e9695/32.png) [@helping-crawdad](https://community.cloudquery.io/u/helping-crawdad)\
**Post date:** [April 16, 2024, 11:28am UTC](https://community.cloudquery.io/t/error-429-too-many-requests-when-downloading-azure-consumption-subscription-legacy-usage-details/252/1 "2024-04-16T11:28:58Z")

</div>

Hi, I am trying to download the table `azure_consumption_subscription_legacy_usage_details` but I keep getting an error:

```auto
RESPONSE 429: 429 Too Many Requests

```

This happens because it makes the calls for each billing period separately. What can I do?

---

<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:** [April 16, 2024, 11:55am UTC](https://community.cloudquery.io/t/error-429-too-many-requests-when-downloading-azure-consumption-subscription-legacy-usage-details/252/2 "2024-04-16T11:55:20Z")

</div>

Hi @helping-crawdad,

You could try setting `concurrency` to a lower level via the Azure plugin spec. For example, try with:

```yaml
concurrency: 1

```

See more in the [CloudQuery Azure Configuration Documentation](https://hub.cloudquery.io/plugins/source/cloudquery/azure/latest/docs#configuration-azure-spec).

If that doesn’t work, can you open a bug report via [GitHub Issues](https://github.com/cloudquery/cloudquery/issues/new?assignees=&labels=kind%2Fbug&projects=&template=bug_report.yml&title=bug%3A+%3Ctitle%3E)? Maybe there’s something we can do to optimize the table further or filter the results.

I’m encountering `429` errors with `azure_consumption_subscription_legacy_usage_details`.