Does this work with dynamic-schedules?

I can't figure out how to use dynamic schedules with this gem, any help will be appreciated.

How is active scheduler supposed to be started after being configured? I'm using Rails 5. is it through rails resque:scheduler ?

hi,
when I use
Resque.enqueue_at(10.seconds.from_now, SendMailJob, :my_id => id)
my job is correctly added to delayed job, then it is added to default queue, then I can see in resque-web that it has been counted as a success but I dont receive any mail
If I do
SendMailJob.perform_later(:my_id => id)

then I receive a mail.

my job:

class SendMailJob < ActiveJob::Base
  queue_as :default
  
  def self.queue
    :default
  end

  def perform(params)
    user = User.find(params[:id])
    ...
  end
end

what am I doing wrong ?

We are running recurring jobs continuously for every 30s but it is working for one day on production after one if schedule the job its not working and not executing the job.

Please help me ASAP.

Thanks for the great gem.

One small issue I ran into. I had a class name that was 41 characters in length which resulted in an app[scheduler.1]: NameError: uninitialized constant on Heroku only (it seemed to work fine in development) when I added the active_scheduler gem.

When I renamed the class so it was now 29 characters in length I no longer received the error on Heroku.

Perhaps some info regarding class name size restrictions could be added to the readme if such a restriction does exist.

I currently set my schedule within an initializer and using this gem causes my jobs to be autoloaded, which in Rails 6 is now deprecated. I'm doing this in an initializer to enable me to use the resque-scheduler web UI. The error I get is below. I was wondering if anyone had any good solutions to this.

Being able to do this is deprecated. Autoloading during initialization is going
to be an error condition in future versions of Rails.

Reloading does not reboot the application, and therefore code executed during
initialization does not run again. So, if you reload ApplicationJob, for example,
the expected changes won't be reflected in that stale Class object.

These autoloaded constants have been unloaded.

Please, check the "Autoloading and Reloading Constants" guide for solutions.

my job class looks something like this:

class MyJob < ApplicationJob
 def perform(arg0 = false, arg1 = 1)
  puts "arg0=#{arg0} ~~~ arg1=#{arg1}"
 end
end

resque_schedule.yml looks like this:

MyJob:
  cron: "* * * * *"
  queue: "default"
  named_args: true
  args:
    - arg0: false
      arg1: 0

but the result is
arg0={arg0: false, arg1: 0} ~~~ arg1=1