We get this happening in Resque sometimes and restarting the worker seems to clear it up. Still annoying though. Have you ever gotten this to run successfully or does it fail immediately?
-- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/xpDmQL3dwA0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
