Open chrisroos opened 7 years ago
We've recently seen the Section::RemoveService::SectionNotFoundError
in production.
My guess is that the user encountered a Publishing API error and then used the browser back button to try again. By which time the Section stored in the local database had been removed.
Steps to reproduce:
RestClient::UnprocessableEntity: 422 Unprocessable Entity
exception is raised from the Publishing APIDespite this exception being raised by the Publishing API the Section will have been deleted from the local manuals-publisher database. This means that it you go "back" in the browser and try to withdraw the section again you'll now see the
Section::RemoveService::SectionNotFoundError
exception. At this point the local database and Publishing API/Content Store are out of sync.