- Algolia Client Version: 2.0.4
- Language Version: ruby-2.7.2
Description
Hi Algolia team:
We recently see logs with message like this Too many indices (xxx > xxx), please remove unused indices before pushing, but it never seems to raise any error from our monitoring tools like Sentry or Rollbar when we use .save_objects
Just wondering if it is that .save_objects only care about success HTTP request but not success of index creation? Thus we need to use .save_objects! instead here?
Steps To Reproduce
Calling .save_objects when almost reaching the limit.
Description
Hi Algolia team:
We recently see logs with message like this
Too many indices (xxx > xxx), please remove unused indices before pushing, but it never seems to raise any error from our monitoring tools like Sentry or Rollbar when we use.save_objectsJust wondering if it is that
.save_objectsonly care about success HTTP request but not success of index creation? Thus we need to use.save_objects!instead here?Steps To Reproduce
Calling
.save_objectswhen almost reaching the limit.