## Context
[Self-Host] After docker-deploying Firecrawl, crawl jobs sit in 'waiting' forever in the UI while /scrape works.
## Verified resolution
Root cause found by contributor kun432: the docker-compose worker service was not running the worker production command, so no worker consumed crawl jobs. Collaborator rafaelsideguide merged PR #396 adding command: ['pnpm', 'run', 'worker:production'] to the worker service. Lesson: 'stuck in waiting' on self-hosted Firecrawl means the crawl worker is not running - check the worker container's command.