Fix ActiveJob::SerializationError: Unsupported argument type: Symbol in Rails

This error occurs when you pass an argument to an ActiveJob that cannot be serialized by the job serializer. ActiveJob uses GlobalID for models and JSON serialization for primitives. Symbols, procs, and complex objects cannot be serialized. Convert symbols to strings and pass simple types or GlobalID-capable models.

Reading the Stack Trace

Here's what each line means:

• activejob (7.1.3) lib/active_job/arguments.rb:80:in `serialize_argument': ActiveJob cannot serialize the Symbol type into a format suitable for the queue backend.
• activejob (7.1.3) lib/active_job/enqueuing.rb:42:in `enqueue': The error occurs when the job is being enqueued, not when it runs.
• app/controllers/reports_controller.rb:12:in `generate': The controller action attempts to enqueue a job with a Symbol argument.

Common Causes

class ReportJob < ApplicationJob
  def perform(report_type)
    Report.generate(report_type)
  end
end

# Controller
ReportJob.perform_later(:monthly)  # Symbol is not serializable

NotificationJob.perform_later(-> { User.active })

data = OpenStruct.new(name: 'report', type: 'pdf')
ExportJob.perform_later(data)

The Fix

Convert the symbol to a string before passing it to perform_later. Inside the job, convert it back to a symbol if needed. Strings are JSON-serializable and work with all queue backends.

ReportJob.perform_later(:monthly)

ReportJob.perform_later('monthly')

# In the job:
class ReportJob < ApplicationJob
  def perform(report_type)
    Report.generate(report_type.to_sym)
  end
end

Testing the Fix

require 'rails_helper'

RSpec.describe ReportJob, type: :job do
  describe '#perform' do
    it 'enqueues with a string argument' do
      expect {
        ReportJob.perform_later('monthly')
      }.to have_enqueued_job(ReportJob).with('monthly')
    end

    it 'generates the correct report type' do
      expect(Report).to receive(:generate).with(:monthly)
      ReportJob.perform_now('monthly')
    end
  end
end

Run your tests:

bundle exec rspec spec/jobs/report_job_spec.rb

Pushing Through CI/CD

git checkout -b fix/rails-serialization-error,git add app/jobs/report_job.rb app/controllers/reports_controller.rb,git commit -m "fix: convert symbol to string for ActiveJob serialization",git push origin fix/rails-serialization-error

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:16
        env:
          POSTGRES_PASSWORD: postgres
        ports: ['5432:5432']
      redis:
        image: redis:7
        ports: ['6379:6379']
    steps:
      - uses: actions/checkout@v4
      - uses: ruby/setup-ruby@v1
        with:
          ruby-version: '3.3'
          bundler-cache: true
      - run: bin/rails db:setup
      - run: bundle exec rspec

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

gem install bugstack

require 'bugstack'

Bugstack.init(api_key: ENV['BUGSTACK_API_KEY'])

Deploying the Fix (Manual Path)

1. Replace all symbol arguments in job enqueue calls with strings.
2. Update jobs to convert strings back to symbols inside perform.
3. Run job specs to confirm serialization works.
4. Open a pull request.
5. Merge and verify jobs process correctly in staging.

Frequently Asked Questions