Heroku API v2 sunsetting - FYI

[dam13n]

If you are getting errors like this, it's because Workless uses the heroku-api gem, which is using a deprecated API. Heroku is running scheduled brown outs (like today), so people are aware of the issue.

Heroku::API::Errors::ErrorWithResponse #some_method
Expected(200) <=> Actual(410 Gone) body: "{\"id\":\"gone\",\"error\":\"This version of the API has been Sunset.\\nPlease see https://devcenter.heroku.com/changelog-items/1147 for more information.\\n\"}"

https://devcenter.heroku.com/changelog-items/1147

[traviskochel]

Ran into this too. This gem worked for me though, and it's actively maintained: https://github.com/davidakachaos/workless_revived/

[unmultimedio]

@traviskochel Hey thanks for the recommendation. Any short guide on how to migrate? Because their README has basically the same guide of installation, so, it would be just changing the gem name in the Gemfile?

You have that gem working on production right now? And it's working as it was Workless before?

UPDATE
I had to use the gem workless_revived because everything was down in production. It has worked good so far, sending background emails and doing background jobs, turning on and off correctly the additional workers.

[traviskochel]

I've got it in production on two apps. The only change you have to make is switch
Delayed::Job.scaler = :heroku_cedar to Delayed::Job.scaler = :heroku, if you're declaring the scaler.

One app is working fine. The other has been acting a little strange though. I was getting a lot of this error for a short period, when starting background jobs:

I wasn't able to find the source, but the issue hasn't come back. Using the same versions of all gems involved in the trace in both apps, and don't see any differences in the config.