Tomasz Mazur

In our scenario, both indexes are used quite intensively: ``` index_good_jobs_on_active_job_id_and_created_at; 12 MB; 540986 (scans) index_good_jobs_on_active_job_id; 800 kB; 133125100 (scans) ``` so, in my opinion both of them fulfill their...

I've experienced the same behavior when the job used all available memory during execution (Heroku). It is impossible to discard (or destroy) such job via GJ dashboard (until worker is...

@stillhart I came up with simple integration for ActiveJob (tested with SolidQueue) https://gist.github.com/defkode/3da234167d1a7bc18a46ff2e700c4d65