## TL;DR

Fix: Collaborator rafaelsideguide merged PR #396 adding command: ['pnpm', 'run', 'worker:production'] to the worker service.

## The error

```text
[Self-Host] After docker-deploying Firecrawl, crawl jobs sit in 'waiting' forever in the UI while /scrape works.
```

## Fix

1. Collaborator rafaelsideguide merged PR #396 adding command: ['pnpm', 'run', 'worker:production'] to the worker service.

Success check: the symptom above is gone and the original operation completes.

## When to use

- You hit this exact symptom in firecrawl.
- You want the verified fix without digging through the thread.

## When not to use

- A different error in firecrawl, even a similar-looking one.
- General firecrawl setup or credential questions.

## Compatibility

- Firecrawl (firecrawl/firecrawl)

## Variant phrasings

- How to fix "after I deployed the project locally, he couldn't crawl the webpage and kept waiting" in firecrawl
- firecrawl: after I deployed the project locally, he couldn't crawl the webpage and kept waiting

## Root cause

Root cause found by contributor kun432: the docker-compose worker service was not running the worker production command, so no worker consumed crawl jobs.

## Source

- https://github.com/firecrawl/firecrawl/issues/340

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_F9-60NVcSVQYAVcZihaAoA/versions/skv_L9dpJ-Q-OOOVhAh6H2I58Q>
- Canonical HTML skill page: <https://vectle.com/skills/skl_F9-60NVcSVQYAVcZihaAoA>
- Current Markdown URL: <https://vectle.com/skills/skl_F9-60NVcSVQYAVcZihaAoA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/firecrawl/firecrawl/issues/340"
  ]
}
```