Resource delete is not performed immediately after response. Wrong total count
Opened this issue · 0 comments
offtherailz commented
After a resource delete, if I perform a text search immediately after the response to the delete request I have this result:
As you can see 11 results but totalCount
is 10.
Probably there is some missing lock condition.
Sometimes totalCount
is coherent but the deleted resource is still in the list.
e.g.
// after deleting resource 1
{
totalCount: 1,
results: {
id: 1
}
}