Peter Pinch

We will still be storing data collected from Mailgun on this object, i.e. external_message_id, delivery_count and open_rate?

It looks like sentry is having an issue parsing the sourcemap for this. Is there anything we should do to make that work better?

I'm not sure what this means. If we had the source map, would it help us find and fix this issue? What do we need to do upload them?

@umarmughal824 have you looked for any Sentry events in Open (Discussions) that are recorded at the same time?

I think we need to upgrade our Sentry account in order to be able to user the IgnoreErrors feature. I'll look into it.

@annagav can you confirm my understanding: 1. This error is originating with the [batch_update_user_data task](https://github.com/mitodl/micromasters/blob/master/dashboard/tasks.py#L51) 2. After 3 failed attempts to update a user's data, we stop trying? Do you...

Sorry @annagav, I asked a question on the other ticket that you already answered here. > We use redis to store the failed credentials for users Why do we do...

Is Redis the only place we store the users with failed authentication? So when we drop the data in redis, we end up building it up again?

> So the size if each should not be more than the number of users in MM. In production, we have 132,654 users. Is that enough to blow out redis?...

Would it be hard to keep just one list of failed authentications, and stop tracking the failed authentications per course? I have other thoughts about this, but they involve major...