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?

Connections

PreviousSettingsNextQueues

Last updated 4 years ago

Was this helpful?

A connection in taskforce represents a connection to a redis instance. Therefore a connection can include none or several queues. The connection panel in the sidebar allows you to view all the queues available in a given redis database and to choose any queue for performing more advanced operations.

Connections can be purchased separately if using external redis hosts, or they are included if you provision your redis instances in Taskforce.sh.

Once you have a working connection it will have a green status icon indicating that the connection has successfully connected to redis. Initially the connection will fetch the queues available in the redis database, however it is necessary to refresh manually if new queues are added or removed.

Sometimes the connection status icon may light red. In this case the connection has lost connectivity with the redis database. We try to give some hint on why this may have happened. If you are unable to sort out the problem, please reach support for assistance.