Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7674539
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T16:45:37+00:00 2026-05-31T16:45:37+00:00

I am having many problems running DJ. Primarily, I cannot get delayed_job running any

  • 0

I am having many problems running DJ. Primarily, I cannot get delayed_job running any methods that change the database. I am testing locally with a sqlite3 database, DJ 3.0.0, and I even added the delayed_job_active_record gem.

I have, for example, tried to run the following method in the background:

 @user = User.find(1)
 @user.delay.recorder_method

Where this method is:

 def recorder_method
    self.relevant_field +=1
    update
 end

This creates a delayed job, and the handler has the appropriate info for the user and the appropriate method name. The script runs the job, thinks it has succeeded and thus deletes the record from the delayed_job table. BUT the user is unchanged (the database is unchanged).

What on earth is going wrong? Note that, when I run the same code (“@user.delay.recorder_method”) from rails console, it works.. and the difference is the handler created by the rails console call is:

 --- !ruby/object:Delayed::PerformableMethod
    object: !ruby/ActiveRecord:User
    attributes:
        ... (attribute info and rest of file)

Whereas the one created in by the call in a controller action is:

 --- !ruby/struct:Delayed::PerformableMethod 
    object: !ruby/ActiveRecord:User 
    attributes: 

Not the difference in line 1 of both things (ruby/object vs ruby/struct.. the former works and the latter doesn’t). Maybe this is something that might signal what is going wrong. Any ideas, anybody?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T16:45:38+00:00Added an answer on May 31, 2026 at 4:45 pm

    For anyone interested, removing the following lines from boot.rb solved this issue for me:

     require 'yaml'
     YAML::ENGINE.yamler = 'syck'
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm having so many problems getting more than 1 MVC project up and running
I'm just wondering if anyone has had any problems having too many subscribers for
I'm having problems with a wordpress install. I've installed many wordress website, and never
I'm having problems with updating a child model via nested form. I've read many
I'm having problems with running my application on Heroku. It always shows me this
I'm having problems with debugging DOM changes introduced by some JavaScript code I'm running.
I am having problems closing an application that uses WaitForSingleObject() with an INFINITE timout.
I've been having a problem that's plagued me many times in the course of
I am having a SP that is doing a select union of many tables
I don't remember having many problems using Cookies in the past but I was

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.