Fix ArgumentError: 'invalid_status' is not a valid status in Rails

This error occurs when you assign a value to an enum attribute that is not in the defined list of valid values. Rails enums only accept declared values and raise an ArgumentError for anything else. Validate the input before assignment or rescue the error and return a meaningful message to the user.

Reading the Stack Trace

Here's what each line means:

• activerecord (7.1.3) lib/active_record/enum.rb:185:in `assert_valid_value': Rails validates the enum value and raises because 'invalid_status' is not in the defined list.
• activerecord (7.1.3) lib/active_record/enum.rb:155:in `cast': The enum type cast method checks the value against the defined mapping.
• app/controllers/orders_controller.rb:18:in `update': The controller update action assigns the invalid status value from user input.

Common Causes

def update
  @order = Order.find(params[:id])
  @order.status = params[:status]  # Could be any string
  @order.save!
end

class Order < ApplicationRecord
  enum status: { pending: 0, processing: 1, shipped: 2, delivered: 3 }
end

@order.status = 'shiped'  # Typo: should be 'shipped'

# Old: enum status: { active: 0, inactive: 1 }
# New: enum status: { enabled: 0, disabled: 1 }
# Database still has 'active' and 'inactive' string values if using string column

The Fix

Check if the provided status is a valid enum value using Order.statuses.key? before assignment. Return a helpful error message listing valid values when the input is invalid.

def update
  @order = Order.find(params[:id])
  @order.status = params[:status]
  @order.save!
end

def update
  @order = Order.find(params[:id])
  if Order.statuses.key?(params[:status])
    @order.update!(status: params[:status])
    render json: @order
  else
    render json: { error: "Invalid status. Valid values: #{Order.statuses.keys.join(', ')}" },
           status: :unprocessable_entity
  end
end

Testing the Fix

require 'rails_helper'

RSpec.describe OrdersController, type: :request do
  let(:order) { create(:order, status: :pending) }

  describe 'PATCH /orders/:id' do
    it 'updates with a valid status' do
      patch "/orders/#{order.id}", params: { status: 'shipped' }
      expect(response).to have_http_status(:ok)
      expect(order.reload.status).to eq('shipped')
    end

    it 'returns error for invalid status' do
      patch "/orders/#{order.id}", params: { status: 'invalid_status' }
      expect(response).to have_http_status(:unprocessable_entity)
      expect(JSON.parse(response.body)['error']).to include('Invalid status')
    end
  end
end

Run your tests:

bundle exec rspec spec/requests/orders_spec.rb

Pushing Through CI/CD

git checkout -b fix/rails-enum-invalid,git add app/controllers/orders_controller.rb,git commit -m "fix: validate enum value before assignment",git push origin fix/rails-enum-invalid

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']
    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. Add enum validation before assignment in all controllers.
2. Write request specs for valid and invalid enum values.
3. Run the full test suite.
4. Open a pull request.
5. Merge and verify in staging.

Frequently Asked Questions