Instead of upserting a member when handling new user creation, just abort. This would have prevented an instance of data corruption that occurred this morning when many users' phases were reset to 1 following the queuing of a bunch of new userCreated jobs that shouldn't have been queued. The jobs were triggered by a migration of user role data in idm.
Instead of upserting a member when handling new user creation, just abort. This would have prevented an instance of data corruption that occurred this morning when many users' phases were reset to 1 following the queuing of a bunch of new
userCreated
jobs that shouldn't have been queued. The jobs were triggered by a migration of user role data inidm
.