Comment 3 for bug 1726474

Normally the situation Blake described would be solved by cascading deletes. However Django implements it's own cascading logic instead of relying on the database, and it doesn't seem to retry in case of errors like these.

Ideally it should be fixed in Django, but maybe we could retry the request if it fails like this?