Duplicate event keys (migration incident)
During initialization of the event url keys (a manual migration procedure), concurrent requests triggered generation of the new event url keys as well. Newly created keys from tx A (the migration) were not considered when determining the new key in tx B, causing multiple events to have the same key. This resulted in wrong URLs for some events.
Fix: regenerate all keys for tracks with duplicate event keys in it.Submitted by Elmer van Chastelet on 23 May 2019 at 16:02