Closed madeleineostoja closed 7 years ago
UPDATE: Looks like if remove
fails like this it also has the potential to break all successive API calls for the project, throwing 400s from the broken UIDs whenever you try to PUT something, even if it doesn't touch those UIDs.
Fixed on 2.0-preview
branch
Haven't pinned down an exact repro yet, but
save()
afterremove()
on an existing UID often fails with a 500 thrown from the new API.There's something that triggers this for a particular UID, and once that UID is 'broken' it can't be removed...