This ticket is being filed on behalf of an Atlas customer that uncovered the following bug. This ticket is the user’s story followed by steps to recreate.

A staff user was working with a pre-existing Resource record and added a component manually (not through the spreadsheet importer). Immediately upon creating the AO, the AO was unavailable and staff saw the "Oops! We're having trouble fetching this tree. Please try refreshing the page." error message when trying to access it. Upon inspecting the db, the AO that was created was assigned to repo 6 despite both its parent AO and parent resource being in repo 5.

• Parent Resource  '/repositories/5/resources/1905': Created 2023-02-01 in Repo 5

• Parent component AO 719314: Created 2023-02-02 in Repo 5

• Problem AO 720597: Created 2023-02-03 15:08:59 in Repo 6

• Top Container assigned to AO 720597: Created a few seconds earlier than the AO at 2023-02-03 15:08:44 in Repo 6

 
The customer reports that this happened twice with the above being the second time; the first time they went in via the API to delete the AO (since it was unavailable in the interface) and then resumed work.
 
A staff member was able to recreate the issue:

1. Open any archival object in a resource in Edit mode

   1. It’s possible that you also have to make a change to this object, but it may not be necessary

2. Open another browser tab or window and change to a different repository

3. Go back to the original tab or window and you’ll see the “Your repository has changed, this record can’t be saved” message. Even though you can’t save, you can add a child or sibling

4. Add a child or sibling, then save that archival object. Now that AO will have a different repository than the rest of the Resource!

 
In conversation with Christine, she said:

This sounds like a bug in the application (in that ArchivesSpace should recognize that the AO repository doesn’t match its parent and actually not save it), with a side of needing user documentation to say “If you change your repository in a different tab, ArchivesSpace expects to work in that repository. You can’t work in two different repositories in the same browser at the same time.”