We made a conscious decision not to use transactions when creating accounts because it would be too slow. There are cases when user that don’t have account created in our database yet comes and performs operation that does many requests, this can lead to this error.

To workaround that, we should catch this error in GetOrCreateByIdentity and try again (just one time) to compensate that. Alternatively since we have caching now, we can use transaction actually. Or using ON CONFLICT statement from Postgresql.

https://glitchtip.devshift.net/insights/issues/793932