You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my dev machine, jobs run correctly and are correctly marked in the dashboard as 'finished', and I can see that performed_at and finished_at are present when printing GoodJob::ActiveJobJob.last in the console. This is true in development both when using the default async execution_mode and also when overriding it with external and running bundle exec good_job start separately.
However when running the same code in staging (Rails.env = production), jobs also run correctly but they always show up as 'unfinished' in the dashboard, and performed_at and finished_at remain nil. How to go about finding the cause of this?
The text was updated successfully, but these errors were encountered:
On my dev machine, jobs run correctly and are correctly marked in the dashboard as 'finished', and I can see that
performed_at
andfinished_at
are present when printingGoodJob::ActiveJobJob.last
in the console. This is true in development both when using the default asyncexecution_mode
and also when overriding it withexternal
and runningbundle exec good_job start
separately.However when running the same code in staging (
Rails.env
=production
), jobs also run correctly but they always show up as 'unfinished' in the dashboard, andperformed_at
andfinished_at
remain nil. How to go about finding the cause of this?The text was updated successfully, but these errors were encountered: