Closed robmadole closed 6 years ago
I'll try and reproduce this and get a better exception later today. That would help a ton.
Yes a full stack trace would definitely be helpful. Thanks!
I'm going to close this for inactivity, though I'd be happy to revisit if there is more information 🙂
Yeah we didn’t see it again. 🤷♂️ Thanks @mitchellhenke
@robmadole cool, thanks for letting me know!
I am running 2.1.3 which includes the
handle_info
method that should take care of this but it's still showing up in our logs. I've double-checked that we are running 2.1.3.The exception from Sentry is:
I wish that I had the entire exception because that would shed a little more light on why this is still occurring.