# Can my Mechanic concurrency limit be raised? Perhaps! This question can come up when the Mechanic queue for a particular store becomes backlogged, delaying task activity. Queue concurrency is controlled by each store's Mechanic [**concurrency limit**](/core/runs/concurrency.md). {% hint style="info" %} In most cases, an inefficient run queue is best addressed by combining or reorganizing tasks, improving [Shopify API usage efficiency](/core/shopify/api-rate-limit.md) (converting REST requests to GraphQL is often helpful), or by making judicious use of [event filters](/platform/events/filters.md). It can be also useful to temporarily disable a task responsible for the backup; doing so will cause Mechanic to instantly fail its enqueued runs when they come up for processing, but it will not fail those task runs ahead of time. {% endhint %} The limit can be evaluated and adjusted on a case-by-case basis with the platform support team. Contact with your shop domain and as many specifics about your scenario as possible, and we can discuss from there. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://learn.mechanic.dev/faq/can-my-mechanic-concurrency-limit-be-raised.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.