Miscellaneous Features
Last synchronized at 2026-01-12T22:47:32Z
CurrentAttributes
Rails’ CurrentAttributes allows you to set request-specific attributes which are accessible to any code executing during that request. For example, you can implement multi-tenancy by setting a tenant_id associated with each request.
Sidekiq supports persisting these attributes into every job payload to preserve any implicit state. Sidekiq will restore these attributes when the job executes.
# Put this in config/initializers/sidekiq.rb
#
require "sidekiq/middleware/current_attributes"
# Your AS::CurrentAttributes singleton, don't use
# the class directly as you shouldn't load app classes
# in your initializers.
Sidekiq::CurrentAttributes.persist("Myapp::Current")
CurrentAttributes are not visible within Sidekiq’s sidekiq_retry_in and sidekiq_retries_exhausted hooks since those hooks are called outside of the middleware context. See issue #6766 for discussion.
- API
- Active-Job
- Advanced-Options
- Batches
- Best-Practices
- Build-vs-Buy
- Bulk-Queueing
- Comm-Installation
- Commercial-FAQ
- Commercial-Support
- Commercial-collaboration
- Complex-Job-Workflows-with-Batches
- Delayed-extensions
- Deployment
- Devise
- Embedding
- Ent-Encryption
- Ent-Historical-Metrics
- Ent-Leader-Election
- Ent-Multi-Process
- Ent-Periodic-Jobs
- Ent-Rate-Limiting
- Ent-Rolling-Restarts
- Ent-Unique-Jobs
- Ent-Web-UI
- Error-Handling
- FAQ
- Getting-Started
- Heroku
- Home
- Iteration
- Job-Format
- Job-Lifecycle
- Kubernetes
- Logging
- Memory
- Metrics
- Middleware
- Miscellaneous-Features
- Monitoring
- Pro-API
- Pro-Expiring-Jobs
- Pro-Metrics
- Pro-Reliability-Client
- Pro-Reliability-Server
- Pro-Web-UI
- Problems-and-Troubleshooting
- Profiling
- Really-Complex-Workflows-with-Batches
- Related-Projects
- Reliability
- Scaling
- Scheduled-Jobs
- Sharding
- Signals
- Testimonials
- Testing
- The-Basics
- Using-Dragonfly
- Using-Redis