Steps:
- Create a feature set
- Retrieve the list of sets from cache endpoint e.g.
/sets (presumably that list is now cached)
- Delete the feature set
- After a reasonable amount of time, retrieve the list of sets again (same as 2.)
Result: the deleted feature set is still in the list.
This is a pretty low severity issue in terms of functionality, but it does mean that the /sets API doesn't return the same data on the cache vs. the origin, which could be significant.