Collection Project changes will not save, "Include Taxa" list keeps duplicating

Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.

Platform (Android, iOS, Website): Website

App version number, if a mobile app issue (shown under Settings or About):

Browser, if a website issue (Firefox, Chrome, etc) : Chrome

URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/projects/cornwall-vermont-selected-wildlife-observations/

Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):


Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):

Step 1: This project was converted from a traditional project to a collection project successfully.

Step 2: When adding taxa and uses under “Include,” they duplicated after saving the project the first time (see screen captures above/ scroll down to taxa on the project page - link above).

Step 3: When I try to go back in and edit the taxa and users that are included, I get the following error:
{“error”:“Not found”}

updates to collection project rules sometimes take a while to save, and if you leave the page while it’s still saving and initiate another change, you can end up with duplicates. i think if you have multiple people making changes at the same time, you can also end up with duplicates. (here’s a previous case where we noted some duplicates: https://forum.inaturalist.org/t/add-user-function-working-properly/22132/10).

i don’t think the duplication actually causes any specific issues other than clutter. you should be able to delete the duplicates without any issue, too.

We found the cause of this and fixed it but you’ll have to add taxa to the project again. They should show up as duplicates when you do. Let me know if you’re able to do that successfully.

We weren’t able to replicate the issue on our end, though, so we’re unsure how it got into the state it was in.

Thanks a ton, the issue is fixed on my end!