Skip to main content
This guide covers common issues you may encounter when using bullstudio and provides solutions to resolve them.

​
Connection Issues

​
Cannot connect to Redis

Symptoms:
  • “Connection timeout” error when adding connection
  • Connection status stuck on “Pending”
Causes:
  • Redis not accessible from bullstudio servers
  • Firewall blocking connection
  • Incorrect hostname or port
Solutions:
  1. Verify Redis is running and accessible
  2. Check firewall/security group rules allow inbound traffic on Redis port
  3. Confirm hostname and port are correct
  4. Verify your Redis instance is publicly accessible
# Test connectivity from your network
redis-cli -h your-redis-host -p 6379 ping
Symptoms:
  • “NOAUTH” or “Authentication required” error
  • “Wrong password” error
Causes:
  • Incorrect password
  • Wrong username for ACL auth
  • User lacks required permissions
Solutions:
  1. Double-check the password
  2. For Redis 6+, ensure correct username is provided
  3. Verify user has read permissions on the queue keys
# Check if authentication works
AUTH your-password
# Or for ACL
AUTH username password
Symptoms:
  • “TLS handshake error”
  • “Certificate verification failed”
Causes:
  • TLS not enabled on Redis
  • Self-signed certificate not provided
  • Wrong port (some providers use different TLS ports)
Solutions:
  1. Confirm TLS is enabled on your Redis instance
  2. For self-signed certs, add CA certificate to connection config
  3. Try port 6380 if 6379 doesn’t work with TLS
Symptoms:
  • Connection shows “Failed” status
  • Error message in connection details
Solutions:
  1. Check the error message in connection details
  2. Use “Test Connection” to diagnose
  3. Review Redis server logs for more details
  4. Verify Redis server is healthy

​
Queue and Job Issues

​
No Queues Appearing

Symptoms:
  • Connection shows “Connected” but no queues appear
  • Queue list is empty
Causes:
  • Connected to wrong Redis database
  • No BullMQ queues exist yet
  • Queues use custom prefix
Solutions:
  1. Verify the database number (default is 0)
  2. Confirm queues exist in Redis
  3. Check if your BullMQ queues use a non-default prefix
# Check for BullMQ keys in Redis
redis-cli keys "bull:*"
Symptoms:
  • Only some queues appear
  • New queues don’t show up
Causes:
  • Queues created after initial connection
  • Different Redis databases
  • Queue prefix mismatch
Solutions:
  1. Refresh the queue list
  2. Check if queues are in different databases
  3. Wait for queue discovery (happens on next activity)

​
Job Issues

Symptoms:
  • Jobs show “Active” for extended periods
  • Active job count keeps growing
Causes:
  • Worker crashed during processing
  • Job is genuinely long-running
  • Worker stalled
Solutions:
  1. Check worker logs for crashes
  2. Configure stalled job handling in BullMQ
  3. Review job processing logic for hanging operations
// Configure stalled job check in BullMQ
const worker = new Worker('queue', processor, {
  stalledInterval: 30000, // Check every 30 seconds
});
Symptoms:
  • Same jobs failing multiple times
  • High attempt counts
Causes:
  • Bug in job processor
  • External service down
  • Invalid job data
Solutions:
  1. Check job error messages and stack traces
  2. Review job data for issues
  3. Verify external services are accessible
  4. Fix bugs and deploy updated worker code
Symptoms:
  • Retry/Remove buttons don’t work
  • “Read-only” error
Causes:
  • Connection is in Read-Only mode
  • Insufficient permissions
Solutions:
  1. Update connection to Read-Write mode
  2. Verify Redis user has write permissions

​
Dashboard and Metrics Issues

Symptoms:
  • Dashboard shows stale data
  • “Last updated” timestamp old
Causes:
  • Connection issue
  • Browser caching
  • Agent disconnected (for proxy connections)
Solutions:
  1. Click the refresh button
  2. Check connection status
  3. Hard refresh the browser (Ctrl+Shift+R)
  4. Verify agent is running (for proxy connections)
Symptoms:
  • Charts are empty
  • “No data” message
Causes:
  • No jobs processed in time range
  • Wrong connection/queue selected
  • Time range too short
Solutions:
  1. Extend the time range
  2. Verify correct connection is selected
  3. Check that jobs are being processed

​
Alert Issues

Symptoms:
  • Alert triggered but no email
  • Test email not received
Causes:
  • Email in spam folder
  • Incorrect email address
  • Alert in cooldown period
Solutions:
  1. Check spam/junk folder
  2. Verify recipient email is correct
  3. Check if alert is in cooldown
  4. Use “Test Alert” to verify configuration
Symptoms:
  • Metrics exceed threshold but no alert
  • Alert status stays “OK”
Causes:
  • Alert disabled
  • Threshold too high
  • Time window hasn’t elapsed
Solutions:
  1. Verify alert is enabled
  2. Check threshold against actual metrics
  3. Wait for time window to complete
  4. Review alert configuration
Symptoms:
  • Receiving constant notifications
  • Alert flapping between triggered/resolved
Causes:
  • Threshold too sensitive
  • Cooldown too short
  • No resolve threshold configured
Solutions:
  1. Increase trigger threshold
  2. Add resolve threshold (lower than trigger)
  3. Increase cooldown period
  4. Use longer time windows

​
Account and Billing Issues

Symptoms:
  • “Limit reached” error
  • Create button disabled
Causes:
  • Plan limit reached
Solutions:
  1. Delete unused workspaces/connections
  2. Upgrade your plan
Symptoms:
  • Alerts tab shows upgrade message
  • Can’t create alerts
Causes:
  • On Free plan
Solutions:
  1. Upgrade to Pro or Enterprise

​
Getting Help

If your issue isn’t covered here:
  1. Check status: Visit our status page for known issues
  2. Search docs: Use the search function to find related topics
  3. Contact support: Email support@bullstudio.dev
When contacting support, include:
  • Your workspace/organization name
  • Connection details and error messages
  • Error messages (screenshots help)
  • Steps to reproduce the issue

​
Next Steps

Connection Setup

Review connection configuration.

Dashboard

Understand dashboard metrics.

Alerts

Configure alert notifications.