> For the complete documentation index, see [llms.txt](https://www.lightward.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lightward.guide/support/samples/mechanic-slowdown.md).

# mechanic slowdown

Subject: queue is increasing

hi\
the current queue is 22hours behind\
earlier it was 17 hours behind.

Some important automations are not working.\
What can we do to clear the queue?\
I have already disabled a few tasks

***

Hi ████,

Thanks for writing in. It's a headache, isn't it? ❤️ We're working on resolving the slowdown, and you can track our progress here:

<https://status.mechanic.dev/incidents/fjk22spwhg67>

And if you'd like to chat with others who are impacted, join our community Slack at <https://slack.mechanic.dev/>. There's a thread in #general right now about this incident.

In the meantime, I raised your Mechanic concurrency limit from 5x to 10x, which should help.

I'm sorry for the trouble — thanks for letting us know that this impacts you. You're important, and so is this. ❤️

With anticipation for a solid fix for this issue,

\=Isaac


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://www.lightward.guide/support/samples/mechanic-slowdown.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.