Closed salmonsteak1 closed 1 week ago
Ah, yes, this is a limitation of the current implementation. I'll make it so that the option to Run now is hidden in this case.
I see, thanks for all the work done on Solid Queue and Mission Control @rosa !
Improved here: https://github.com/rails/mission_control-jobs/pull/202
Clicking on "Run now" for scheduled tasks can't work if we're running Mission Control on a separate instance that does not contain the main codebase. Seems like it's because Mission Control is calling the queue adapter's
enqueue
method. It then eventually hits this line of code:But since the job class isn't defined on this separate instance, an exception is thrown. Here's the full stack trace: