Explore out of memory messages and updated registration invite job #4696
Comments
|
From the "Too much memory used at runtime" section, it's recommended to use Scout to help troubleshoot memory leak/usage issues. We already have the Scout add-on in Heroku, but we disabled it when we were doing the last Rails update (866fba9 which references the issue #2872). Anywho, I'll add Scout back in to hopefully give us some insights (I'm not sure I want to officially assign myself to this issue, but getting Scout hooked up should be a good start I think). |
This update will make it so that the `UpdateRegistrationInviteJob` will only get called if an invite code exists. I think this should help with all the failed jobs that don't have an invite code. Refs: #4696
|
I think I have the failed registration invite jobs fixed (once it gets to Production). I added a condition to only call the job if an invite code exists, which should address this issue. I actually had already made the same fix on Preview when I was working on assigning chapter ambassador to the chapter (associated to the invite code) after they registered. |
This update will make it so that the `UpdateRegistrationInviteJob` will only get called if an invite code exists. I think this should help with all the failed jobs that don't have an invite code. Refs: #4696
No description provided.
The text was updated successfully, but these errors were encountered: