If an event is already on the schedule and people have queued it, and then the event's registration policy changes the keys of its buckets, existing signups, signup requests, and queue items that reference those bucket keys can become invalid. We saw this happen for the first round of signups at A Larp Festival 2026.
When an existing event is changing its registration policy in a way that removes an existing bucket, Intercode should check for existing records that reference that bucket. If there are any, it should present a UI that asks the user to map old buckets to new buckets before proceeding, so it can update all the existing records that reference that bucket.
If an event is already on the schedule and people have queued it, and then the event's registration policy changes the keys of its buckets, existing signups, signup requests, and queue items that reference those bucket keys can become invalid. We saw this happen for the first round of signups at A Larp Festival 2026.
When an existing event is changing its registration policy in a way that removes an existing bucket, Intercode should check for existing records that reference that bucket. If there are any, it should present a UI that asks the user to map old buckets to new buckets before proceeding, so it can update all the existing records that reference that bucket.