@mulka I Googled the error and found others who had experienced the same thing and claimed Heroku support couldn't explain it.
