# Extra rate limit options

**URL:** <https://forum.alumio.com/t/extra-rate-limit-options/549>\
**Category:** Feature Requests\
**Created:** [April 13, 2023, 8:15am UTC](https://forum.alumio.com/t/extra-rate-limit-options/549 "2023-04-13T08:15:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Alumio\_Bot](https://forum.alumio.com/user_avatar/forum.alumio.com/alumio_bot/32/1824_2.png) [@Alumio\_Bot](https://forum.alumio.com/u/Alumio_Bot)\
**Post date:** [April 26, 2023, 8:59am UTC](https://forum.alumio.com/t/extra-rate-limit-options/549/5 "2023-04-26T08:59:44Z")

</div>

I-am not sure if it’s applicable for your issue, but @jesse posted two ideas on a similar topic.  
With the addition of reading rate limit headers.

> [@Alumio Task: Single threaded](https://forum.alumio.com/t/alumio-task-single-threaded/541/2):
>
> Hi @abubakar, Within a single route Alumio should never process the tasks multi-threaded. I suppose you are running into a problem with rate limiting. You can do two things: First thing I would check is whether the API returns a header that gives information about ratelimiting. An example header would be: X-RateLimit-Minutely-Remaining: 60 This header indicates that I can send another 60 requests during this minute. With each subsequent request, the number goes down. During the next minute…

@Gugi Some extra information.

---

_[View the full topic](https://forum.alumio.com/t/extra-rate-limit-options/549)._