Delete blocker does not show up initially

[chanulee1]

Describe the bug
When trying to delete an agent record without the initial warning that there is a delete blocker in place, the loading screen for checking for delete blockers runs for a couple of minutes before the delete blocker warning appears. Alternatively, when the delete button is not clicked, an error message appears after a few minutes.

Possible relation to #1748?

To Reproduce
Steps to reproduce the behavior:

1. Go to the agent record without the initial delete blocker warning
2. Click "Delete"
3. Wait on loading screen for a few minutes
4. Delete blocker warning then appears

Alternatively:

1. Go to the agent record without the initial delete blocker warning
2. Wait for a few minutes
3. Error message appears:
   Specify 7 Crash Report - 2022-09-27T21_19_20.759Z.txt

Expected behavior
Expected the agent record to be deleted if not referenced by a field. If referenced by a field, expected a delete blocker warning to appear initially before the deletion attempt.

Screenshots
An agent record without the delete blocker warning

When "Delete" button is clicked, the loading screen appears

After a couple of minutes, the delete blocker warning then appears

Console:
Console

Alternatively, when the "Delete" button is not clicked, the error message appears after a few minutes

Console:
Console

Desktop:

• OS: Windows 10
• Browser: Chrome
• Specify 7 Version: 7.7.3

Database Name: KUBirds
User: spbirdadmin
Specific record: Robbins, Mark https://kubirds-v773-prerelease.test.specifysystems.org/specify/view/agent/1/

Reported By
Name of your institution

Additional context
Database name or any other context about the problem here.

[maxpatiiuk]

The server responded with a 502 error.
This usually indicates that the test server is reloading, thus this is a temporary issue
Can you try reproducing this again?

[chanulee1]

I was able to reproduce it, with the same error message. As far as I can tell, it seems to happen only for the record Robbins, Mark in the KUBirds database.

[melton-jason]

Might be fixed in #2806

[emenslin]

This behavior is inconsistent, originally assumed it had to do with spusers but not all users throw the error.

To recreate this, in the lsumammals database the users spadmin and jake throw errors whereas users like austin and testuser do not. I did not check every single user but I am not sure what the underlying cause might be

Error message with some users:

Specify 7 Crash Report - 2024-05-31T14_44_34.352Z.txt

Deletion blocker with other users: