Yeah. It's a tough one. However people do often (obviously based on sentry) attempt to use non-existent message IDs (usually an unsupported lang). So once that happened that message ID would be invalid until the next basket push. This seems like a Bad Thing:tm: to require IT involvement to enable a new message ID. That said, the time out could be pretty long. 12 hours would be fine I'd think. We might even be able to ad an admin action to clear the cache manually if we really needed it to be live immediately.

A `locmem` cache would be super nice for this. Perhaps we could do the following in `settings/__init__.py`:

```python
CACHES['message_ids'] = {
    'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
    'TIMEOUT': 12 * 60 * 60,  # 12 hours
}
```

We'd have to do it in `__init__.py` so that it would be appended to the `CACHES` setting from IT in their `local.py`.