perf: Optimize detecting deleted conversation after a backup restore [WPB-6166] #16678
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
After a successful backup restore, we try to locally delete conversations that are deleted on backend.
Previously we didn't have a way to get those deleted conversation other than querying every single conversation and checking if the response is a
404
on backend.Now we can optimize this and query all the conversations at once and check which ones are
not_found
.Checklist