There seem to be two issues at play: an insert of a measurement into a time-series collection where a bucket has been removed manually may result in a bucket update that matches no buckets, but does not generate an error even though it should.
Possible solutions for this issue may include having an OpObserver invalidate buckets belonging to a time-series collections on direct operations on the bucket collection. Alternatively we can do that on detecting an error in the update.