Worker
also: workers, background worker, worker process
A program that runs separately from your main app and works through the tasks waiting in a queue.
A process that pulls jobs from a queue and executes them, one or several at a time. Workers usually run and scale separately from the web server, so heavy work doesn't slow page loads. Browsers also have "web workers", which run scripts off the page's main thread.
The cooks in a kitchen. Orders pile up on the ticket rail, which is the queue. Cooks take them one at a time. Busy night? Add more cooks.
If your agent adds a queue, something must run the worker. If the worker isn't deployed or has crashed, jobs pile up and nothing happens, with no visible error.
The queue is set up, but you'll need to run a worker in production too: add a second process on Render with the command npm run worker.
How will the worker run in production, and how will we know if it crashes? Add a health check and tell me exactly what to set up on the host.
Assuming the worker starts automatically with the web app. Usually it's a separate process that must be deployed and kept running.