Taskforce.sh
  • Documentation
  • Getting started
    • Direct Redis Connection
    • Taskforce connector
  • Account
    • Settings
  • Connections
    • Queues
    • Jobs
    • Workers
  • Metrics
  • Monitoring
    • Enable notifications
      • Slack
      • Pagerduty
    • Connection monitor
    • Failed jobs monitor
    • Missing workers monitor
    • Max Memory monitor
    • Backlog Monitor
  • Alerts
  • Organizations
  • BullMQ Pro
    • Connector Pro
  • On Premises
    • AWS
      • Launch AWS AMI.
      • Create role with SSM permissions
      • Assign SSM Role
      • Configure your instance
        • Create a PostgreSQL instance
        • Configure Auth0
          • Configure API
        • Configure Mailgun
      • Setup loadbalancer
      • Setup route 53
      • Monitors
      • Upgrading
      • Troubleshooting
    • Docker
      • Docker registry
      • Environment variables
      • Docker compose
    • Using the taskforce connector
  • Security primer
  • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Connections

Workers

PreviousJobsNextMetrics

Last updated 4 years ago

Was this helpful?

The workers view gives you a list of all the actually workers connected to a given queue. This is quite useful so that you can verify that the intended amount of workers are really connected and processing jobs. If the list is missing some expected workers it could be that these workers are offline or lost connection to the redis database.

The workers represent actual workers instances connected to Redis, independently on the concurrency setting used in the workers.

Currently due to an underlaying issue in Bull/BullMQ the workers table will show incorrect results if you are reusing connections.