Added error handling for if special group not found for special event

[jasoncavanaugh]

This is a quick fix since this error is bringing the entire page down. In the future, we would want more granular handling of error states in the UI.

[railway-app[bot]]

This PR is being deployed to Railway 🚅

admin-portal: ◻️ REMOVED

[jasoncavanaugh]

I haven't looked at it deeply, but I would guess the error is related to the fact that every special group is really a special event in Airtable. We do some processing of the Airtable data in our code to make it seem like there is just one event with multiple groups, but it's really multiple events with each special group being its own special event. However, there is still a special groups table. So a Saturday event = general event + (number of special groups attending) * special event. In this particular instance, we are linking up the ids of special groups found in the special events table with special groups fetched from the special groups table. This involves matching ids from different Airtable tables, and the error was happening because a special group id that was in the special events table was not being found in the special groups table.

Additionally, this kind of error shouldn't be taking down the whole app, so in the future, we should try and make the error states more granular.

[mattsahn]

I haven't looked at it deeply, but I would guess the error is related to the fact that every special group is really a special event in Airtable. We do some processing of the Airtable data in our code to make it seem like there is just one event with multiple groups, but it's really multiple events with each special group being its own special event. However, there is still a special groups table. So a Saturday event = general event + (number of special groups attending) * special event. In this particular instance, we are linking up the ids of special groups found in the special events table with special groups fetched from the special groups table. This involves matching ids from different Airtable tables, and the error was happening because a special group id that was in the special events table was not being found in the special groups table.

Additionally, this kind of error shouldn't be taking down the whole app, so in the future, we should try and make the error states more granular.

Yeah, this is ringing a bell. @hgreenhut, I remember talking about how to best handle the special event concept and unify everything, but that was a big change to pull off. Not that we need to change that, but should look into this case of what broke on the data side. This is at least the second time this scenario came up.